From: Russell King <linux@armlinux.org.uk>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
linux-perf-users@vger.kernel.org, loongarch@lists.linux.dev,
Mark Rutland <mark.rutland@arm.com>,
Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
James Clark <james.clark@linaro.org>,
Huacai Chen <chenhuacai@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Oleg Nesterov <oleg@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Waiman Long <longman@redhat.com>, WANG Xuerui <kernel@xen0n.name>,
Will Deacon <will@kernel.org>,
Clark Williams <clrkwllms@kernel.org>
Subject: Re: [PATCH v2] ARM, ARM64, LONGARCH: Delay HW BP notification to task_work()
Date: Mon, 7 Sep 2026 15:46:09 +0100 [thread overview]
Message-ID: <ap7OMYBVKUrQjX9O@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260904155404.ESPFg3zi@linutronix.de>
On Fri, Sep 04, 2026 at 05:54:04PM +0200, Sebastian Andrzej Siewior wrote:
> On 2026-09-03 13:31:46 [-0400], Steven Rostedt wrote:
> > On Thu, 3 Sep 2026 17:47:24 +0100
> > Russell King <linux@armlinux.org.uk> wrote:
> >
> > > What do you expect to happen with this? Which arch maintainer should
> > > apply this patch that affects three different independently maintained
> > > architectures?
>
> Well, if you as the ARM person are fine with ARM part, an ACK would be
> appreciated. If you have something to object, it would be nice to let me
> know so I can adjust accordingly.
First, I only just looked at the email - you may have noticed I'm not
very active with the kernel anymore, as I'm a full-time carer at the
moment.
Second, I'm not fine with the patch as-is, because it's not clear how
it could be merged in its current form. It would be inappropriate to
give an Ack, because an Ack means I'm fine with it. I'm not.
Third, I haven't actually reviewed the patch itself (see first point).
Looking deeper now, I see nothing in the linked report, nor in your
write-up that identifies what is responsible for the context being
inappropriate to deliver the SIGTRAP. See the first point - I'm not
able to read lots of code to work that out, and presumably you've
already done that ground work to come up with a fix. This is *vital*
information when someone looks back at why this change was made as
it helps to understand how the problem occurs. This is, after all,
the whole point of commit messages - to help people look back and
understand why a change was made. The "what the changes are" part
is already covered by the patch showing what the changes were. It's
the stuff that *isn't* in the patch that needs to be in the commit
message.
So... don't describe the code changes in a commit message.
So no, an Ack is not appropriate.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2026-09-07 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 8:51 Sebastian Andrzej Siewior
2026-08-14 9:03 ` sashiko-bot
2026-08-14 9:20 ` Sebastian Andrzej Siewior
2026-09-03 15:47 ` Luis Claudio R. Goncalves
2026-09-03 16:07 ` Sebastian Andrzej Siewior
2026-09-03 16:47 ` Russell King
2026-09-03 17:31 ` Steven Rostedt
2026-09-04 15:54 ` Sebastian Andrzej Siewior
2026-09-07 14:46 ` Russell King [this message]
2026-09-08 7:54 ` Sebastian Andrzej Siewior
2026-09-08 8:00 ` Russell King
2026-09-08 8:37 ` Sebastian Andrzej Siewior
2026-09-08 8:43 ` Russell King
2026-09-08 9:38 ` Sebastian Andrzej Siewior
2026-09-08 12:47 ` Russell King
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=ap7OMYBVKUrQjX9O@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=clrkwllms@kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kernel@xen0n.name \
--cc=lgoncalv@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=longman@redhat.com \
--cc=loongarch@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®