From: Mark Brown <broonie@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mhocko@suse.cz, sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: mmotm 2022-02-23-21-20 uploaded
Date: Fri, 25 Feb 2022 02:11:28 +0000 [thread overview]
Message-ID: <Yhg60P06ksKTjddP@sirena.org.uk> (raw)
In-Reply-To: <20220223212416.c957b713f5f8823f9b8e0a8d@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Wed, Feb 23, 2022 at 09:24:16PM -0800, Andrew Morton wrote:
> On Wed, 23 Feb 2022 21:21:36 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > The mm-of-the-moment snapshot 2022-02-23-21-20 has been uploaded to
> >
> > https://www.ozlabs.org/~akpm/mmotm/
> >
>
> Below is how I resolved the fallout from jamming today's linux-next
> back on top of the MM queue.
Thanks, this was enormously helpful (there's a bunch of embarrassing
merge fixups in the tree today, but they're all driver error with me fat
fingering the scripts).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-25 2:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 5:21 Andrew Morton
2022-02-24 5:24 ` Andrew Morton
2022-02-25 2:11 ` Mark Brown [this message]
2022-02-25 6:37 ` Andrew Morton
2022-02-26 1:43 ` Mark Brown
2022-02-24 17:13 ` mmotm 2022-02-23-21-20 uploaded (Kconfig warning: SND_SOC_WCD938X) Randy Dunlap
2022-03-03 22:39 ` Randy Dunlap
2022-02-24 17:46 ` mmotm 2022-02-23-21-20 uploaded (iwlwifi + rfkill) Randy Dunlap
2022-02-24 17:53 ` mmotm 2022-02-23-21-20 uploaded (kernel/sched/rt.c) Randy Dunlap
2022-02-24 18:04 ` mmotm 2022-02-23-21-20 uploaded [drivers/scsi/hisi_sas/hisi_sas_main.ko] Randy Dunlap
2022-02-24 18:22 ` John Garry
2022-02-24 18:17 ` mmotm 2022-02-23-21-20 uploaded [drivers/net/wireless/intel/iwlwifi/iwlwifi.ko][2] Randy Dunlap
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=Yhg60P06ksKTjddP@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=willy@infradead.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