From: Pengfei Li <lpf.vector@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christopher Lameter <cl@linux.com>,
penberg@kernel.org, David Rientjes <rientjes@google.com>,
iamjoonsoo.kim@lge.com, Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <guro@fb.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] mm, slab: Make kmalloc_info[] contain all types of names
Date: Tue, 8 Oct 2019 22:21:38 +0800 [thread overview]
Message-ID: <CAD7_sbFvsXMMa9zHiV9SvaXYnrX6zoo9X5e09ToLupcx1=U8=Q@mail.gmail.com> (raw)
In-Reply-To: <20191002160649.9ab76eabaf5900548c455b02@linux-foundation.org>
On Thu, Oct 3, 2019 at 7:06 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Mon, 23 Sep 2019 20:27:25 +0800 Pengfei Li <lpf.vector@gmail.com> wrote:
>
> > Changes in v6
> > --
> > 1. abandon patch 4-7 (Because there is not enough reason to explain
> > that they are beneficial)
>
> So http://lkml.kernel.org/r/20190923004022.GC15734@shao2-debian can no
> longer occur?
>
Sorry for such a late reply.
Yes, it‘s caused by [patch v5 5/7]. So do not occur in v6.
> > Changes in v5
> > --
> > 1. patch 1/7:
> > - rename SET_KMALLOC_SIZE to INIT_KMALLOC_INFO
> > 2. patch 5/7:
> > - fix build errors (Reported-by: kbuild test robot)
> > - make all_kmalloc_info[] static (Reported-by: kbuild test robot)
> > 3. patch 6/7:
> > - for robustness, determine kmalloc_cache is !NULL in
> > new_kmalloc_cache()
> > 4. add ack tag from David Rientjes
> >
>
>
>
prev parent reply other threads:[~2019-10-08 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 12:27 [PATCH v6 0/3] mm, slab: Make kmalloc_info[] contain all types of names Pengfei Li
2019-09-23 12:27 ` [PATCH v6 1/3] " Pengfei Li
2019-09-23 12:27 ` [PATCH v6 2/3] mm, slab: Remove unused kmalloc_size() Pengfei Li
2019-09-23 12:27 ` [PATCH v6 3/3] mm, slab_common: Use enum kmalloc_cache_type to iterate over kmalloc caches Pengfei Li
2019-10-02 23:06 ` [PATCH v6 0/3] mm, slab: Make kmalloc_info[] contain all types of names Andrew Morton
2019-10-08 14:21 ` Pengfei Li [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='CAD7_sbFvsXMMa9zHiV9SvaXYnrX6zoo9X5e09ToLupcx1=U8=Q@mail.gmail.com' \
--to=lpf.vector@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=guro@fb.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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).