From: Shaokun Zhang <zhangshaokun@hisilicon.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <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>, <sfr@canb.auug.org.au>,
jinyuqi <jinyuqi@huawei.com>
Subject: Re: mmotm 2019-12-06-19-46 uploaded
Date: Wed, 11 Dec 2019 09:42:09 +0800 [thread overview]
Message-ID: <f4596325-a5cd-935e-38a3-61ca36aae9ae@hisilicon.com> (raw)
In-Reply-To: <20191210173507.5f4b46bde9586456c2132560@linux-foundation.org>
Hi Andrew,
On 2019/12/11 9:35, Andrew Morton wrote:
> On Mon, 9 Dec 2019 14:31:55 +0800 Shaokun Zhang <zhangshaokun@hisilicon.com> wrote:
>
>> Hi Andrew,
>>
>> About this patch,
>> https://lore.kernel.org/lkml/1573091048-10595-1-git-send-email-zhangshaokun@hisilicon.com/
>>
>> It is not in linux-next or your trees now, has it been dropped?
>
> Yes, I dropped it with a "to be updated" note. Michal is asking for
> significant changelog updates (at least).
Ok, Shall I rebase on 5.5-rc1 and send patch v4?
Thanks,
Shaokun
>
>
> .
>
next prev parent reply other threads:[~2019-12-11 1:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191206170123.cb3ad1f76af2b48505fabb33@linux-foundation.org>
2019-12-07 3:47 ` mmotm 2019-12-06-19-46 uploaded Andrew Morton
2019-12-09 6:31 ` Shaokun Zhang
2019-12-11 1:35 ` Andrew Morton
2019-12-11 1:42 ` Shaokun Zhang [this message]
2019-12-11 1:58 ` Andrew Morton
2019-12-11 3:14 ` mmotm 2019-12-10-19-14 uploaded Andrew Morton
2019-12-11 16:31 ` mmotm 2019-12-10-19-14 uploaded (objtool: func() falls through) Randy Dunlap
2019-12-12 18:48 ` Josh Poimboeuf
[not found] ` <042c6cd7-c983-03f1-6a79-5642549f57c4@infradead.org>
2019-12-12 20:58 ` Josh Poimboeuf
2020-01-17 18:11 ` Josh Poimboeuf
2020-01-17 22:15 ` Randy Dunlap
2019-12-18 4:41 ` mmotm 2019-12-17-20-41 uploaded 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=f4596325-a5cd-935e-38a3-61ca36aae9ae@hisilicon.com \
--to=zhangshaokun@hisilicon.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=jinyuqi@huawei.com \
--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 \
/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).