From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Xin Li <xin@zytor.com>
Cc: Gavin Shan <gshan@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-acpi@vger.kernel.org, James Morse <james.morse@arm.com>,
loongarch@lists.linux.dev, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
jianyong.wu@arm.com, justin.he@arm.com,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Salil Mehta <salil.mehta@huawei.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-ia64@vger.kernel.org
Subject: Re: [PATCH] cpu-hotplug: provide prototypes for arch CPU registration
Date: Tue, 3 Oct 2023 19:09:26 +0100 [thread overview]
Message-ID: <ZRxY1l+79XqOHZk1@shell.armlinux.org.uk> (raw)
In-Reply-To: <7aee5021-8bb6-4343-b746-a8417af030a9@zytor.com>
On Tue, Oct 03, 2023 at 10:37:02AM -0700, Xin Li wrote:
> On 10/3/2023 7:34 AM, Russell King (Oracle) wrote:
> > > > >
> > > > > Signed-off-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> > > > > ---
> > > > > Changes since RFC v2:
> > > > > - drop ia64 changes, as ia64 has already been removed.
> > > > >
>
> If this is RFC v2, we put "RFC v2" in the subject, then people know you
> are sending a newer version.
Sorry, but this is yet another illustration why the kernel process is
broken. Clearly, people do NOT bother reading what is actually written,
but instead make up in their minds something completely different.
This is *NOT* RFC v2. This is RFC v2:
https://lore.kernel.org/all/E1qgnh2-007ZRZ-WD@rmk-PC.armlinux.org.uk/
And what I wrote was "changes **** SINCE **** RFC v2". For those who
find English difficult, this means that what follows is the list of
changes that are in THIS posting that WERE NOT IN THE PREVIOUS POSTING
which was RFC v2.
Thanks for making me even more frustrated than I was.
> People are busy, and your patch could be
> skipped if it appears the same as a previous one.
Yet another reason why the kernel process is just completely broken.
"appears to be". Even when the changes are spelled out. Yes, right,
people don't have time to read. If that's the case, then it's a
waste of time adding a change log. It's a waste of time to add a
commit message. In fact, it's a total waste of time trying to
contribute to a rotten-to-the-core open source project that Linux
seems to have turned into.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-03 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 16:28 [PATCH] cpu-hotplug: provide prototypes for arch CPU registration Russell King (Oracle)
2023-09-25 23:04 ` Gavin Shan
2023-09-25 23:17 ` Russell King (Oracle)
2023-10-03 14:34 ` Russell King (Oracle)
2023-10-03 17:37 ` Xin Li
2023-10-03 18:09 ` Russell King (Oracle) [this message]
2023-10-10 16:23 ` Russell King (Oracle)
2023-10-11 12:06 ` Thomas Gleixner
2023-10-11 13:08 ` Tomáš Glozar
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=ZRxY1l+79XqOHZk1@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gshan@redhat.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=jean-philippe@linaro.org \
--cc=jianyong.wu@arm.com \
--cc=justin.he@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=salil.mehta@huawei.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xin@zytor.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 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).