linux-kernel - Re: [PATCH 0/8] staging: sm750fb: change function naming style

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2025040840-domain-boasting-81ec@gregkh>
Date: Tue, 8 Apr 2025 12:47:14 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Richard Akintola <princerichard17a@...il.com>
Cc: Samuel Abraham <abrahamadekunle50@...il.com>, outreachy@...ts.linux.dev,
	sudipm.mukherjee@...il.com, teddy.wang@...iconmotion.com,
	linux-fbdev@...r.kernel.org, linux-staging@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/8] staging: sm750fb: change function naming style

On Tue, Apr 08, 2025 at 11:38:28AM +0100, Richard Akintola wrote:
> On Mon, Apr 7, 2025 at 7:01 AM Greg KH <gregkh@...uxfoundation.org> wrote:
> >
> > On Mon, Apr 07, 2025 at 06:57:38AM +0100, Richard Akintola wrote:
> > > On Sat, Apr 5, 2025 at 3:16 PM Samuel Abraham
> > > <abrahamadekunle50@...il.com> wrote:
> > >
> > > > This looks like a new version of a previously submitted patch, but you
> > > >   did not list below the --- line any changes from the previous version.
> > > >   Please read the section entitled "The canonical patch format" in the
> > > >   kernel file, Documentation/process/submitting-patches.rst for what
> > > >   needs to be done here to properly describe this.
> > >
> > >
> > > Hi Samuel,
> > >
> > > I sent the patches individually before, but I was instructed to send a
> > > patch series.
> > >
> > > Given that I didn't change any code, should I still add version number
> > > and sending
> > > patch series as the difference?
> >
> > Yes.
> >
> > Think about it from our side, what would you want to see if you had to
> > review hundreds of different patches a day?
> >
> > thanks,
> >
> > greg k-h
> 
> Hi Greg,
> 
> I have sent the new version, please do have a look at it.

Again, please realize that some of us get hundreds, if not thousands, of
changes a day to review.  A normal delay is about 1-2 weeks to get to a
review of a change.  Ideally it would be faster, but there are only so
many hours in a day.

To help make this faster, please help out in reviewing other changes
submitted by other developers, that will cause your changes to bubble
up.

thanks,

greg k-h