From: Luis Chamberlain <mcgrof@kernel.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jessica Yu <jeyu@kernel.org>, Borislav Petkov <bp@alien8.de>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [PATCH v3 0/2] background initramfs unpacking, and CONFIG_MODPROBE_PATH
Date: Mon, 15 Mar 2021 20:23:05 +0000 [thread overview]
Message-ID: <20210315202305.GC4332@42.do-not-panic.com> (raw)
In-Reply-To: <20210313212528.2956377-1-linux@rasmusvillemoes.dk>
On Sat, Mar 13, 2021 at 10:25:26PM +0100, Rasmus Villemoes wrote:
> Routing-wise, I hope akpm can handle both patches. Andrew, Luis?
I think it would be ideal for it to go through Andrew's tree.
Luis
prev parent reply other threads:[~2021-03-15 20:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 21:25 [PATCH v3 0/2] background initramfs unpacking, and CONFIG_MODPROBE_PATH Rasmus Villemoes
2021-03-13 21:25 ` [PATCH v3 1/2] init/initramfs.c: do unpacking asynchronously Rasmus Villemoes
2021-03-15 20:21 ` Luis Chamberlain
2021-03-15 21:33 ` Andrew Morton
2021-03-15 21:59 ` Rasmus Villemoes
2021-07-24 7:46 ` Alexander Egorenkov
2021-07-26 11:46 ` Rasmus Villemoes
2021-07-27 7:31 ` Bruno Goncalves
2021-07-27 13:54 ` Luis Chamberlain
2021-07-27 14:12 ` Bruno Goncalves
2021-07-27 14:21 ` Luis Chamberlain
2021-07-27 14:27 ` Bruno Goncalves
2021-07-27 14:42 ` Luis Chamberlain
2021-07-27 14:48 ` Bruno Goncalves
2021-07-28 10:44 ` Alexander Egorenkov
2021-07-28 10:38 ` Alexander Egorenkov
2021-07-28 10:36 ` Alexander Egorenkov
2021-07-28 11:49 ` Rasmus Villemoes
2021-03-13 21:25 ` [PATCH v3 2/2] modules: add CONFIG_MODPROBE_PATH Rasmus Villemoes
2021-03-15 20:06 ` Luis Chamberlain
2021-03-15 20:23 ` Luis Chamberlain [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=20210315202305.GC4332@42.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ndesaulniers@google.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).