All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christopher Lameter <cl@linux.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: SLUB: purpose of sysfs events on cache creation/removal
Date: Thu, 9 Jan 2020 21:15:08 +0100	[thread overview]
Message-ID: <20200109201508.GY4951@dhcp22.suse.cz> (raw)
In-Reply-To: <20200109114415.cf01bd3ad30c5c4aec981653@linux-foundation.org>

On Thu 09-01-20 11:44:15, Andrew Morton wrote:
> On Thu, 9 Jan 2020 15:52:36 +0100 Michal Hocko <mhocko@kernel.org> wrote:
> 
> > On Mon 06-01-20 15:51:26, Cristopher Lameter wrote:
> > > On Mon, 6 Jan 2020, Michal Hocko wrote:
> > > 
> > > > On Wed 04-12-19 18:32:24, Michal Hocko wrote:
> > > > > [Cc akpm - the email thread starts
> > > > > http://lkml.kernel.org/r/20191126121901.GE20912@dhcp22.suse.cz]
> > > >
> > > > ping.
> > > 
> > > There does not seem to be much of an interest in the patch?
> > 
> > It seems it has just fallen through cracks.
> 
> I looked at it - there wasn't really any compelling followup.

Btw. I would appreciate if this was explicit because if there is no
reaction then it is not clear whether the patch has slipped through
cracks or it is not worth pursuing for whatever reason.

Thanks!
-- 
Michal Hocko
SUSE Labs

  parent reply	other threads:[~2020-01-09 20:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 12:19 SLUB: purpose of sysfs events on cache creation/removal Michal Hocko
2019-11-26 16:32 ` Christopher Lameter
2019-11-26 16:54   ` Michal Hocko
2019-11-27 15:40     ` Christopher Lameter
2019-11-27 16:24       ` Michal Hocko
2019-11-27 16:26         ` Christopher Lameter
2019-11-27 17:43           ` Michal Hocko
2019-12-04 13:28             ` Michal Hocko
2019-12-04 15:25               ` Christopher Lameter
2019-12-04 15:32                 ` Michal Hocko
2019-12-04 16:53                   ` Christopher Lameter
2019-12-04 17:32                     ` Michal Hocko
2020-01-06 11:57                       ` Michal Hocko
2020-01-06 15:51                         ` Christopher Lameter
2020-01-06 15:51                           ` Christopher Lameter
2020-01-09 14:52                           ` Michal Hocko
2020-01-09 19:44                             ` Andrew Morton
2020-01-09 20:13                               ` Michal Hocko
2020-01-09 20:15                               ` Michal Hocko [this message]
2020-01-17 17:13                               ` Michal Koutný
2020-01-19  0:15                                 ` Andrew Morton
2020-01-27 17:33                                   ` Michal Koutný
2020-01-27 23:04                                     ` Christopher Lameter
2020-01-27 23:04                                       ` Christopher Lameter
2020-01-28  8:51                                       ` Michal Koutný
2020-01-28 18:13                                         ` Christopher Lameter
2020-01-28 18:13                                           ` Christopher Lameter
2020-01-30 13:16                                           ` Vlastimil Babka
2020-01-09 14:07                     ` Vlastimil Babka

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=20200109201508.GY4951@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.