From: Al Viro <viro@zeniv.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-arch@vger.kernel.org, linux-api@vger.kernel.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
Jan Kara <jack@suse.com>,
linux-fsdevel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] compat: lift compat_s64 and compat_u64 to <asm-generic/compat.h>
Date: Thu, 17 Sep 2020 17:50:49 +0100 [thread overview]
Message-ID: <20200917165049.GV3421308@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200917074159.2442167-2-hch@lst.de>
On Thu, Sep 17, 2020 at 09:41:57AM +0200, Christoph Hellwig wrote:
> lift the compat_s64 and compat_u64 definitions into common code using the
> COMPAT_FOR_U64_ALIGNMENT symbol for the x86 special case.
OK... Unlike the previous series it's not trying to wean arm64 off the
direct includes of asm/compat.h, avoiding the breakage you've got there.
Looks sane, applied.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-17 16:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 7:41 improve compat handling for the i386 u64 alignment quirk v3 Christoph Hellwig
2020-09-17 7:41 ` [PATCH 1/3] compat: lift compat_s64 and compat_u64 to <asm-generic/compat.h> Christoph Hellwig
2020-09-17 15:05 ` Arnd Bergmann
2020-09-17 16:50 ` Al Viro [this message]
2020-09-17 7:41 ` [PATCH 2/3] compat: add a compat_need_64bit_alignment_fixup() helper Christoph Hellwig
2020-09-17 7:41 ` [PATCH 3/3] quota: simplify the quotactl compat handling Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2020-07-31 12:21 improve compat handling for the i386 u64 alignment quirk v2 Christoph Hellwig
2020-07-31 12:22 ` [PATCH 1/3] compat: lift compat_s64 and compat_u64 to <asm-generic/compat.h> Christoph Hellwig
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=20200917165049.GV3421308@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).