From: Marco Elver <elver@google.com>
To: Will Deacon <will@kernel.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
"David S. Miller" <davem@davemloft.net>,
Mark Rutland <mark.rutland@arm.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
sparclinux <sparclinux@vger.kernel.org>
Subject: Re: [PATCH 3/3] arm64: Add compile-time asserts for siginfo_t offsets
Date: Wed, 26 May 2021 19:50:41 +0200 [thread overview]
Message-ID: <CANpmjNOOW6-8su=VNipvb7ztQ0TdF9THn+yeWepz7D7BAL418Q@mail.gmail.com> (raw)
In-Reply-To: <20210526174217.GB19898@willie-the-truck>
On Wed, 26 May 2021 at 19:42, Will Deacon <will@kernel.org> wrote:
> Hi Marco,
>
> On Thu, Apr 29, 2021 at 09:07:34PM +0200, Marco Elver wrote:
> > To help catch ABI breaks at compile-time, add compile-time assertions to
> > verify the siginfo_t layout.
> >
> > Signed-off-by: Marco Elver <elver@google.com>
> > ---
> > arch/arm64/kernel/signal.c | 36 ++++++++++++++++++++++++++++++++++++
> > arch/arm64/kernel/signal32.c | 36 ++++++++++++++++++++++++++++++++++++
> > 2 files changed, 72 insertions(+)
>
> Do you want me to queue this patch in the arm64 tree, or is the series all
> going together via another route?
I think Eric will queue them together with a bunch of other cleanups,
because as-is these patches are out-of-date as of:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0e31f3a38e77612ed8967aaad28db6d3ee674b5
Thanks,
-- Marco
next prev parent reply other threads:[~2021-05-26 17:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 19:07 [PATCH 1/3] sparc64: Add compile-time asserts for siginfo_t offsets Marco Elver
2021-04-29 19:07 ` [PATCH 2/3] arm: " Marco Elver
2021-04-29 19:07 ` [PATCH 3/3] arm64: " Marco Elver
2021-05-26 17:42 ` Will Deacon
2021-05-26 17:50 ` Marco Elver [this message]
2021-05-26 18:29 ` Will Deacon
2021-07-02 8:51 ` Marco Elver
2021-07-12 10:38 ` Marco Elver
2021-04-30 17:42 ` [PATCH 1/3] sparc64: " Eric W. Biederman
2021-04-30 18:11 ` Marco Elver
2021-04-30 22:22 ` David Miller
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='CANpmjNOOW6-8su=VNipvb7ztQ0TdF9THn+yeWepz7D7BAL418Q@mail.gmail.com' \
--to=elver@google.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=sparclinux@vger.kernel.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).