From: Andrew Morton <akpm@linux-foundation.org>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Michal Hocko <mhocko@suse.com>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Thomas Garnier <thgarnie@google.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>,
Steven Rostedt <rostedt@goodmis.org>,
Joel Fernandes <joelaf@google.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Tejun Heo <tj@kernel.org>
Subject: Re: [RFC PATCH v2 0/1] improve vmap allocation
Date: Mon, 1 Apr 2019 15:59:39 -0700 [thread overview]
Message-ID: <20190401155939.66ad1f8ad999fde514002e66@linux-foundation.org> (raw)
In-Reply-To: <20190401110347.aby2v6tvqfvhyupf@pc636>
On Mon, 1 Apr 2019 13:03:47 +0200 Uladzislau Rezki <urezki@gmail.com> wrote:
> Hello, Andrew.
>
> >
> > It's a lot of new code. I t looks decent and I'll toss it in there for
> > further testing. Hopefully someone will be able to find the time for a
> > detailed review.
> >
> I have got some proposals and comments about simplifying the code a bit.
> So i am about to upload the v3 for further review. I see that your commit
> message includes whole details and explanation:
>
> http://git.cmpxchg.org/cgit.cgi/linux-mmotm.git/commit/?id=b6ac5ca4c512094f217a8140edeea17e6621b2ad
>
> Should i base on and keep it in v3?
>
It's probably best to do a clean resend at this stage. I'll take a
look at the deltas and updating changelogs, etc.
next prev parent reply other threads:[~2019-04-01 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 19:03 [RFC PATCH v2 0/1] improve vmap allocation Uladzislau Rezki (Sony)
2019-03-21 19:03 ` [RFC PATCH v2 1/1] mm/vmap: keep track of free blocks for " Uladzislau Rezki (Sony)
2019-03-22 21:54 ` Roman Gushchin
2019-03-25 17:20 ` Uladzislau Rezki
2019-03-26 14:51 ` Uladzislau Rezki
2019-03-27 0:41 ` Roman Gushchin
2019-03-27 17:52 ` Uladzislau Rezki
2019-03-21 22:01 ` [RFC PATCH v2 0/1] improve " Andrew Morton
2019-03-22 16:52 ` Uladzislau Rezki
2019-03-22 17:47 ` Joel Fernandes
2019-04-01 11:03 ` Uladzislau Rezki
2019-04-01 22:59 ` Andrew Morton [this message]
2019-04-02 8:48 ` Uladzislau Rezki
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=20190401155939.66ad1f8ad999fde514002e66@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mingo@elte.hu \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.com \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).