From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Matthew Wilcox <willy@infradead•org>
Cc: akpm@linux-foundation•org, broonie@kernel•org,
linux-fsdevel@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-mm@kvack•org, linux-next@vger•kernel.org, mhocko@suse•cz,
mm-commits@vger•kernel.org
Subject: Re: mmotm 2021-03-08-21-52 uploaded
Date: Wed, 10 Mar 2021 07:56:23 +1100 [thread overview]
Message-ID: <20210310075623.303ce786@canb.auug.org.au> (raw)
In-Reply-To: <20210309204502.GL3479805@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 877 bytes --]
Hi Matthew,
On Tue, 9 Mar 2021 20:45:02 +0000 Matthew Wilcox <willy@infradead•org> wrote:
>
> On Mon, Mar 08, 2021 at 09:52:55PM -0800, akpm@linux-foundation•org wrote:
> > The mm-of-the-moment snapshot 2021-03-08-21-52 has been uploaded to
> >
> > https://www.ozlabs.org/~akpm/mmotm/
> ...
> > This mmotm tree contains the following patches against 5.12-rc2:
> > (patches marked "*" will be included in linux-next)
>
> Something seems to have gone wrong in next-20210309. There are a number
> of patches listed here which are missing, and some patches are included
> that aren't listed here.
>
> > * mm-use-rcu_dereference-in-in_vfork.patch
>
> This was the one I noticed was missing.
I haven't done a linux-next with this new mmotm yet, it arrived after I
finished 20210309. It will be included today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-09 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 5:52 mmotm 2021-03-08-21-52 uploaded akpm
2021-03-09 6:11 ` Stephen Rothwell
2021-03-09 20:45 ` Matthew Wilcox
2021-03-09 20:56 ` Stephen Rothwell [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=20210310075623.303ce786@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=broonie@kernel$(echo .)org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mhocko@suse$(echo .)cz \
--cc=mm-commits@vger$(echo .)kernel.org \
--cc=willy@infradead$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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