From: "lipeifeng@oppo.com" <lipeifeng@oppo.com>
To: akpm <akpm@linux-foundation.org>, michel <michel@lespinasse.org>
Cc: hughd <hughd@google.com>, linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Barry Song" <21cnbao@gmail.com>,
zhangshiming <zhangshiming@oppo.com>,
peifengl55 <peifengl55@gmail.com>
Subject: Re: Re: [PATCH] mm: fix align-error when get_addr in unmapped_area_topdown
Date: Mon, 2 May 2022 11:33:18 +0800 [thread overview]
Message-ID: <2022050211305415626916@oppo.com> (raw)
In-Reply-To: 20220501181041.6d53cb9ed54bf697840e36cc@linux-foundation.org
Hi Andrew：
Thanks for your quick response.
> They caused me some merge issues against mapletree, which I had
> resolved. Mapletree is dropped at present so I set these patches aside
> until the next version of the mapletree patches are available.
Do we have a definite time for the next available version of the mapletree patches?
Excuse me, is it possible for our patch to be independent of mapletree and brought in separately?
> I've been holding your patches until Michel Lespinasse has had time to
> review them (and hopefully explain them to me ;)). Please review
> earlier comments which Michel has provided and ensure that those
> comments have been fully addressed so we can hopefully move forward on
> this.
We will reply soon if Mr.Lespinasse provideds any advices or question.
And I haven't received any reply from Mr.Lespinasse yet, pls let me know
if i missed the reply.
Thank you very much indeed.
lipeifeng@oppo.com
From: Andrew Morton
Date: 2022-05-02 09:10
To: lipeifeng@oppo.com
CC: michel; hughd; linux-mm; linux-kernel; Barry Song; zhangshiming; peifengl55
Subject: Re: [PATCH] mm: fix align-error when get_addr in unmapped_area_topdown
On Sun, 1 May 2022 10:26:35 +0800 "lipeifeng@oppo.com" <lipeifeng@oppo.com> wrote:
> Why did the two patches suddenly disappear without any email or notice for us?
> And they had been merged in linux-next.git on April 5 and 13.
They caused me some merge issues against mapletree, which I had
resolved. Mapletree is dropped at present so I set these patches aside
until the next version of the mapletree patches are available.
I've been holding your patches until Michel Lespinasse has had time to
review them (and hopefully explain them to me ;)). Please review
earlier comments which Michel has provided and ensure that those
comments have been fully addressed so we can hopefully move forward on
this.
next prev parent reply other threads:[~2022-05-02 3:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 8:10 [PATCH] mm: fix align-error when get_addr in unmapped_area_topdown lipeifeng
2022-04-12 21:22 ` Andrew Morton
[not found] ` <2022041310411426044561@oppo.com>
2022-05-01 2:26 ` lipeifeng
2022-05-02 1:10 ` Andrew Morton
2022-05-02 3:33 ` lipeifeng [this message]
2022-05-07 21:59 ` Andrew Morton
2022-05-09 9:23 ` lipeifeng
2022-05-09 11:45 ` Michel Lespinasse
2022-05-16 2:43 ` lipeifeng
2022-05-16 7:45 ` Michel Lespinasse
2022-05-17 8:04 ` lipeifeng
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=2022050211305415626916@oppo.com \
--to=lipeifeng@oppo.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michel@lespinasse.org \
--cc=peifengl55@gmail.com \
--cc=zhangshiming@oppo.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