public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>,
	Pavel Begunkov <[email protected]>,
	io-uring Mailing List <[email protected]>
Cc: Bedirhan KURT <[email protected]>,
	Louvian Lyndal <[email protected]>
Subject: Re: [PATCHSET v3 liburing 0/3] Add nolibc support for x86-64 arch
Date: Sun, 10 Oct 2021 09:11:31 -0600	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 10/10/21 7:53 AM, Ammar Faizi wrote:
> Hi,
> 
> This is the patchset v3 to add support liburing nolibc x86-64. If you
> think there is more to be fixed, please let me know, I will be happy
> to address it.
> 
> In this patchset, I introduce nolibc support for x86-64 arch.
> Hopefully, one day we can get support for other architectures as well.
> 
> Motivation:
> Currently liburing depends on libc. We want to make liburing can be
> built without libc.
> 
> This idea firstly posted as an issue on the liburing GitHub
> repository here: https://github.com/axboe/liburing/issues/443

Applied, thanks.

-- 
Jens Axboe


      parent reply	other threads:[~2021-10-10 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10 13:53 [PATCHSET v3 liburing 0/3] Add nolibc support for x86-64 arch Ammar Faizi
2021-10-10 13:53 ` [PATCH v3 liburing 1/3] Add arch dependent directory and files Ammar Faizi
2021-10-10 13:53 ` [PATCH v3 liburing 2/3] Add nolibc build support Ammar Faizi
2021-10-10 13:53 ` [PATCH v3 liburing 3/3] configure: Add `CONFIG_NOLIBC` variable and macro Ammar Faizi
2021-10-10 15:11 ` Jens Axboe [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox