From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-vk1-f169.google.com (mail-vk1-f169.google.com [209.85.221.169]) by gnuweeb.org (Postfix) with ESMTPS id 609027E795 for ; Mon, 16 Jan 2023 04:18:26 +0000 (UTC) Authentication-Results: gnuweeb.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=PebSSrjq; dkim-atps=neutral Received: by mail-vk1-f169.google.com with SMTP id z190so12819197vka.4 for ; Sun, 15 Jan 2023 20:18:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QLo9yAHsHm94mDVBHYQdPCAGmoHnGdGAbajlskQEFlU=; b=PebSSrjq4KC1GIm7zyXdpU3BlpeF9Ezg2A2wGYiV3WBIA8VYOfBfH5+YOwxuW3q4Lg 6Lkwfyds4pZjHFDeWAvQbXMASWTkY8bWHbgzyx6reMTn6BieXHFB+cPkPrdpR21WvfXg ivsBtzqdxYy7NqxXjdA9MdjfCpbG0//g+r5R1vZYT868UsgfRAoAydU3wzLlGL1x2X2B p6Tny1EbMeWiUEoSHnka0VlLxp6LEanSsFOaw8SV8umC8gWpseiUX5KF4vUcD61S+8HB QPnbGNj28m7ic1yk4WI4hodYKCtSOXegWShm8QbNpEZkWWF9BNW4Hg6Gj0WuuV9B3mtB PNvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QLo9yAHsHm94mDVBHYQdPCAGmoHnGdGAbajlskQEFlU=; b=m3EGrV4M97gkmb1bca+nX5fIUCcKlds4uRcrxqXKQwZ+Xfhe6ALd2GSRkFoA6k0wlI ipDbt6AIZrErMivNeK92fdaQ91aj1nNvRBFQNuj95MiUTRP6WC+tQxkQ7rzFBqjE/bCq DyOcdWehuqH1SOgBdiLsNTlStEBskNgP3qUwcJDv1l0n84DeDZ1K51rxVCRCfIqExVO4 bYWEFohpP16juFAp+hFhTecMxE28hCvf+ZDB/UTY+BmD3+g7BjOBOr6TrEvuyy8VVDl+ 2QxAwyEX9y6FGtVwNNWZp9yjzKxqKu0GY1QEH2NAoNu/t5htKUw3EJ7EwNbQEVFjkXNP 9vnA== X-Gm-Message-State: AFqh2ko9xax+qbJaOZaaEuo2SLMF8jKk8mMJLFcuGKOXeDoFb+XlABQP kAFuG3CtUM7A9NGc24wO45vE3zSbgjNs3bU1pCc= X-Google-Smtp-Source: AMrXdXtkm3CGx8KlHvZlG6aAh8AauqHXO6gljquIbdBVSJxE2iu4ppyCWaErOJKfoGBX8/C0thM5VMZhcJtuT9YJqK4= X-Received: by 2002:a1f:17d0:0:b0:3dd:fa8a:7a36 with SMTP id 199-20020a1f17d0000000b003ddfa8a7a36mr768436vkx.33.1673842705234; Sun, 15 Jan 2023 20:18:25 -0800 (PST) MIME-Version: 1.0 References: <20230114095523.460879-1-ammar.faizi@intel.com> <20230114095523.460879-3-ammar.faizi@intel.com> <3d217e11-2732-2b85-39c5-1a3e2e3bb50b@kernel.dk> <34a2449a-8500-4081-dc60-e6e45ecb1680@kernel.dk> In-Reply-To: <34a2449a-8500-4081-dc60-e6e45ecb1680@kernel.dk> From: Christian Mazakas Date: Sun, 15 Jan 2023 20:18:14 -0800 Message-ID: Subject: Re: [RFC PATCH v1 liburing 2/2] README: Explain about FFI support To: Jens Axboe Cc: Ammar Faizi , Pavel Begunkov , Gilang Fachrezy , io-uring Mailing List , VNLX Kernel Department , "GNU/Weeb Mailing List" Content-Type: text/plain; charset="UTF-8" List-Id: Hmm, how about something more like this: +Because liburing's main public interface lives entirely in liburing.h as `static inline` +functions, users wishing to consume liburing purely as a binary dependency should +link against liburing-ffi. liburing-ffi contains definitions for every `static inline` function +in liburing.h. - Christian