From: Thomas Gleixner <tglx@linutronix.de>
To: Brian Gerst <brgerst@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>, "H . Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Brian Gerst <brgerst@gmail.com>
Subject: Re: [PATCH 0/2] x86: Clean up ia32_unistd.h
Date: Mon, 19 Jun 2023 23:16:41 +0200 [thread overview]
Message-ID: <87mt0vp2yu.ffs@tglx> (raw)
In-Reply-To: <20230619194745.80552-1-brgerst@gmail.com>
Brian!
On Mon, Jun 19 2023 at 15:47, Brian Gerst wrote:
> Other than one unused macro, ia32_unistd.h is just a wrapper for
> unistd_32_ia32.h, and can be removed.
>
> Brian Gerst (2):
> x86/syscall/compat: Remove unused macro __SYSCALL_ia32_NR
> x86/syscall/compat: Remove ia32_unistd.h
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Thanks a lot for doing this (thankless) cleanup work!
tglx
prev parent reply other threads:[~2023-06-19 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 19:47 [PATCH 0/2] x86: Clean up ia32_unistd.h Brian Gerst
2023-06-19 19:47 ` [PATCH 1/2] x86/syscall/compat: Remove unused macro __SYSCALL_ia32_NR Brian Gerst
2023-06-19 19:47 ` [PATCH 2/2] x86/syscall/compat: Remove ia32_unistd.h Brian Gerst
2023-06-19 21:16 ` Thomas Gleixner [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 \
--in-reply-to=87mt0vp2yu.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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