From: Arnd Bergmann <arnd@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Arnd Bergmann <arnd@arndb.de>, kernel test robot <lkp@intel.com>,
palmerdabbelt@google.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] asm-generic: mark __{get,put}_user_fn as __always_inline
Date: Tue, 27 Oct 2020 16:14:53 +0100 [thread overview]
Message-ID: <160381164874.4082358.6150613146628051056.b4-ty@arndb.de> (raw)
In-Reply-To: <20201027085017.3705228-1-hch@lst.de>
From: Arnd Bergmann <arnd@arndb.de>
On Tue, 27 Oct 2020 09:50:17 +0100, Christoph Hellwig wrote:
> Without the explicit __always_inline, some RISC-V configs place the
> functions out of line, triggering the BUILD_BUG_ON checks in the
> function.
Applied to asm-generic-fixes, thanks!
[1/1] asm-generic: mark __{get,put}_user_fn as __always_inline
commit: 0bcd0a2be8c9ef39d84d167ff85359a49f7be175
Arnd
prev parent reply other threads:[~2020-10-27 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 8:50 [PATCH] asm-generic: mark __{get,put}_user_fn as __always_inline Christoph Hellwig
2020-10-27 15:14 ` Arnd Bergmann [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=160381164874.4082358.6150613146628051056.b4-ty@arndb.de \
--to=arnd@kernel.org \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=palmerdabbelt@google.com \
/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).