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@xxxxxxxxxxxxxxx> > > > > > --- > > > > > 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@xxxxxxxxxxxxxxxxxxxxxx/ 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!
|