public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: GNU/Weeb Mailing List <[email protected]>,
	io-uring Mailing List <[email protected]>,
	Alviro Iskandar Setiawan <[email protected]>,
	Ammar Faizi <[email protected]>
Subject: [PATCH liburing] arch/x86/syscall: Remove TODO comment
Date: Thu, 21 Apr 2022 14:52:30 +0700	[thread overview]
Message-ID: <[email protected]> (raw)

From: Ammar Faizi <[email protected]>

nolibc support for x86 32-bit has been added in commit b7d8dd8bbf5b855
("arch/x86/syscall: Add x86 32-bit native syscall support"). But I
forgot to remove the comment that says "We can't use CONFIG_NOLIBC for
x86 (32-bit)".

Remove it.

Signed-off-by: Ammar Faizi <[email protected]>
---

Hi Jens,

Hopefully, this is the last x86 changes before v2.2 release.

 src/arch/x86/syscall.h | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/src/arch/x86/syscall.h b/src/arch/x86/syscall.h
index 8cd24dd..43c576b 100644
--- a/src/arch/x86/syscall.h
+++ b/src/arch/x86/syscall.h
@@ -144,12 +144,6 @@
 
 #else /* #if defined(__x86_64__) */
 
-/*
- * For x86 (32-bit), fallback to libc wrapper.
- * We can't use CONFIG_NOLIBC for x86 (32-bit) at the moment.
- *
- * TODO: Add x86 (32-bit) nolibc support.
- */
 #ifdef CONFIG_NOLIBC
 /**
  * Note for syscall registers usage (x86, 32-bit):
-- 
Ammar Faizi


             reply	other threads:[~2022-04-21  7:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  7:52 Ammar Faizi [this message]
2022-04-21 12:28 ` [PATCH liburing] arch/x86/syscall: Remove TODO comment Jens Axboe

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] \
    /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