From: Andrew Morton <akpm@linux-foundation.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
Arnd Bergmann <arnd@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Wei Yang <richard.weiyang@linux.alibaba.com>,
Arnd Bergmann <arnd@arndb.de>, Vlastimil Babka <vbabka@suse.cz>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Brian Geffon <bgeffon@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] mm/mremap: fix BUILD_BUG_ON() error in get_extent
Date: Fri, 5 Feb 2021 13:02:23 -0800 [thread overview]
Message-ID: <20210205130223.37e6bf7fb8bfc773db9b5fda@linux-foundation.org> (raw)
In-Reply-To: <20210205190005.GB461042@localhost>
On Fri, 5 Feb 2021 12:00:05 -0700 Nathan Chancellor <nathan@kernel.org> wrote:
> > > > Reviewed-by: Nathan Chancellor <natechancellor@gmail.com>
> > >
> > > Ping? It is pretty late into the 5.11 cycle and this is still broken.
> >
> > I think we should just do the __always_inline. Who can take this?
>
> This should probably go through -mm, unless we get an ack then Nick and
> I could take it.
I added it to -mm on Wednesday.
next prev parent reply other threads:[~2021-02-05 21:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-30 15:40 Arnd Bergmann
2021-01-04 11:34 ` Vlastimil Babka
2021-01-04 22:36 ` Nathan Chancellor
2021-01-05 10:28 ` Arnd Bergmann
2021-01-12 19:16 ` Nathan Chancellor
2021-01-12 20:19 ` Sedat Dilek
2021-02-03 18:48 ` Nathan Chancellor
2021-02-03 20:03 ` Kees Cook
2021-02-05 19:00 ` Nathan Chancellor
2021-02-05 21:02 ` Andrew Morton [this message]
2021-02-05 21:27 ` Nathan Chancellor
2021-02-05 18:33 ` Nick Desaulniers
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=20210205130223.37e6bf7fb8bfc773db9b5fda@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=0x7f454c46@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bgeffon@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=richard.weiyang@linux.alibaba.com \
--cc=vbabka@suse.cz \
/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