mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Sean Anderson <seanga2@gmail.com>
Cc: Yinan Zhang <zhangyinan2019@email.szu.edu.cn>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools/vm/page_owner_sort.c: add switch between culling by stacktrace and txt
Date: Tue, 22 Mar 2022 11:03:27 -0700	[thread overview]
Message-ID: <20220322110327.eb9df4333d25eda837d80a85@linux-foundation.org> (raw)
In-Reply-To: <0f3fca6a-cd9d-a5f7-2eda-3e3a9ceae564@gmail.com>

On Mon, 21 Mar 2022 23:55:29 -0400 Sean Anderson <seanga2@gmail.com> wrote:

> On 3/21/22 10:22 PM, Yinan Zhang wrote:
> > I replied to the email a few months ago. Did you receive it?
> 
> The patch was applied anyway. Anything in this subsystem gets
> applied within a day or two regardless of feedback. Personally,
> I'm not motivated to review anything because of that.
> 

The feedback wasn't ignored, as you're seeing here.

If the feedback appears to be non-fatal I'll hold onto the patch with
an expectation that the feedback will be addressed and we can move
forward with an updated version of the code.


  reply	other threads:[~2022-03-22 18:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29 14:56 Yinan Zhang
2021-11-30  2:23 ` Sean Anderson
2022-03-21 20:38   ` Andrew Morton
     [not found]     ` <623932d3.1c69fb81.e3278.ab09SMTPIN_ADDED_BROKEN@mx.google.com>
2022-03-22  3:55       ` Sean Anderson
2022-03-22 18:03         ` Andrew Morton [this message]
     [not found]     ` <623932d7.1c69fb81.31089.1923SMTPIN_ADDED_BROKEN@mx.google.com>
2022-03-22 18:00       ` Andrew Morton
     [not found]   ` <623a8074.1c69fb81.33a39.0d6cSMTPIN_ADDED_BROKEN@mx.google.com>
2022-03-23 19:08     ` Andrew Morton
     [not found]       ` <623bc151.1c69fb81.12d57.ef3cSMTPIN_ADDED_BROKEN@mx.google.com>
2022-03-24 23:15         ` 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=20220322110327.eb9df4333d25eda837d80a85@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanga2@gmail.com \
    --cc=zhangyinan2019@email.szu.edu.cn \
    /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

all inboxes | Powered by JetHome®