From: Liam Howlett <liam.howlett@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>, Stephen Rothwell <sfr@canb.auug.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the char-misc.current tree with the mm-hotfixes tree
Date: Fri, 19 Aug 2022 22:02:53 +0000 [thread overview]
Message-ID: <20220819220243.ieq3drqvg3lcmark@revolver> (raw)
In-Reply-To: <20220819133539.f8eb934e29e8f4f72c62752b@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> [220819 16:35]:
> On Fri, 19 Aug 2022 13:35:04 +0000 Liam Howlett <liam.howlett@oracle.com> wrote:
>
> > b3bb668f3dc6 is the older v1 of the patch [1]. d6f35446d076 from
> > mm-hotfixes is the correct v2 version [2], although I don't think that's
> > currently in mm-hotfixes-unstable. It looks like version 1 is now in
> > mm-hotfixes-unstable as well.
> >
> > 1: https://lore.kernel.org/linux-mm/20220809160618.1052539-1-Liam.Howlett@oracle.com/
> > 2: https://lore.kernel.org/linux-mm/20220810160209.1630707-1-Liam.Howlett@oracle.com/
>
> I moved "binder_alloc: add missing mmap_lock calls when using the VMA"
> into mm-hotfixes-stable this week.
>
> It's the v2. I intend to send this Linuswards today or tomorrow. Below.
>
> So I think we're all good.
>
>
> commit b3bb668f3dc6a97a91c47a4cebb0e3f33554c08c
...
Sounds good, as long as it isn't the above commit which is v1, but
d6f35446d076 which is v2 :)
Thanks,
Liam
next prev parent reply other threads:[~2022-08-19 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 22:28 linux-next: manual merge of the char-misc.current tree with the mm-hotfixes tree Stephen Rothwell
2022-08-19 6:36 ` Greg KH
2022-08-19 8:40 ` Stephen Rothwell
2022-08-19 8:55 ` Greg KH
2022-08-19 13:35 ` Liam Howlett
2022-08-19 15:44 ` Greg KH
2022-08-19 20:35 ` Andrew Morton
2022-08-19 22:02 ` Liam Howlett [this message]
2022-08-19 22:55 ` Andrew Morton
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=20220819220243.ieq3drqvg3lcmark@revolver \
--to=liam.howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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