From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, wuchi.zero@gmail.com,
syzbot+7937ba6a50bdd00fffdf@syzkaller.appspotmail.com,
swboyd@chromium.org, peterz@infradead.org,
penguin-kernel@I-love.SAKURA.ne.jp, akpm@linux-foundation.org
Subject: Re: + debugobjects-turn-off-debug_objects_enabled-from-debug_objects_oom.patch added to mm-nonmm-unstable branch
Date: Wed, 07 Jun 2023 00:56:36 +0200 [thread overview]
Message-ID: <87y1kwjj2z.ffs@tglx> (raw)
In-Reply-To: <20230530203045.91EAAC433D2@smtp.kernel.org>
Andrew!
On Tue, May 30 2023 at 13:30, Andrew Morton wrote:
> The patch titled
> Subject: debugobjects: turn off debug_objects_enabled from debug_objects_oom()
> has been added to the -mm mm-nonmm-unstable branch. Its filename is
> debugobjects-turn-off-debug_objects_enabled-from-debug_objects_oom.patch
Why the heck are you applying random patches within a day without giving
the people who care and understand this code the chance to actually
review it?
You are well aware that I'm taking care of this since day one despite
that I'm not explicitely mentioned in the MAINTAINERS file. I'm going to
fix that now despite the fact that I want to reduced the number of
entries instead of increasing them...
Aside of that can you please fix your notification mechanism so that the
"I picked that up/dropped it/or whatever" mail shows up in the actual
submission mail thread?
Connecting these '+/- $subject' mails to the actual submission thread is
a pain. It's not rocket science to fix that. patchwork, tip-bot and
others do that for years.
Thanks,
tglx
prev parent reply other threads:[~2023-06-06 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 20:30 + debugobjects-turn-off-debug_objects_enabled-from-debug_objects_oom.patch added to mm-nonmm-unstable branch Andrew Morton
2023-06-06 22:56 ` Thomas Gleixner [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=87y1kwjj2z.ffs@tglx \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=swboyd@chromium.org \
--cc=syzbot+7937ba6a50bdd00fffdf@syzkaller.appspotmail.com \
--cc=wuchi.zero@gmail.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 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.