From: Sasha Levin <sashal@kernel.org>
To: Hugh Dickins <hughd@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Yang Shi <shy828301@gmail.com>,
Wang Yugui <wangyugui@e16-tech.com>,
Xu Yu <xuyu@linux.alibaba.com>, Jue Wang <juew@google.com>,
Matthew Wilcox <willy@infradead.org>, Alex Shi <alexs@kernel.org>,
Miaohe Lin <linmiaohe@huawei.com>, Michal Hocko <mhocko@suse.com>,
stable@vger.kernel.org
Subject: Re: mm/thp commits: please wait a few days
Date: Mon, 28 Jun 2021 23:27:05 -0400 [thread overview]
Message-ID: <YNqTCV7DmYGZiZ7N@sashalap> (raw)
In-Reply-To: <366846c0-245a-771e-7a1-4a307ac6e5e1@google.com>
On Mon, Jun 28, 2021 at 10:12:57AM -0700, Hugh Dickins wrote:
>On Mon, 28 Jun 2021, Greg Kroah-Hartman wrote:
>> So could you just send a mbox of patches (or tarball), for the 4.19,
>> 4.14, and 4.9 trees? That would make it much easier to ensure I got
>> them all correct.
>
>At risk of irritating you, sorry, I am resisting: the more data I send
>you, the more likely I am to mess it up in some stupid way. Please ask
>again and I shall, but I think your success with 5.12, 5.10, 5.4 just
>means that you were right to take a break before 4.19, 4.14, 4.4.
I've tried following the instructions for 4.19, and that worked fine on
my end too.
If no one objects, I can pick up 4.9-4.19 after the current set of
kernels is released.
--
Thanks,
Sasha
next prev parent reply other threads:[~2021-06-29 3:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 23:02 mm/thp commits: please wait a few days Hugh Dickins
2021-06-17 4:51 ` Greg Kroah-Hartman
2021-06-23 14:58 ` Greg Kroah-Hartman
2021-06-23 16:44 ` Hugh Dickins
2021-06-23 16:53 ` Greg Kroah-Hartman
2021-06-23 20:46 ` Andrew Morton
2021-06-23 21:52 ` Hugh Dickins
2021-06-26 0:38 ` Hugh Dickins
2021-06-28 12:17 ` Greg Kroah-Hartman
2021-06-28 17:12 ` Hugh Dickins
2021-06-29 3:27 ` Sasha Levin [this message]
2021-06-29 6:08 ` Greg Kroah-Hartman
2021-06-29 6:51 ` Hugh Dickins
2021-07-01 19:47 ` Hugh Dickins
2021-07-02 11:56 ` Sasha Levin
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=YNqTCV7DmYGZiZ7N@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=juew@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linmiaohe@huawei.com \
--cc=mhocko@suse.com \
--cc=shy828301@gmail.com \
--cc=stable@vger.kernel.org \
--cc=wangyugui@e16-tech.com \
--cc=willy@infradead.org \
--cc=xuyu@linux.alibaba.com \
/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