[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Yh8ytrK7EJjYbrHF@mail.google.com>
Date: Wed, 2 Mar 2022 22:02:46 +1300
From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@...il.com>
To: Dan Carpenter <dan.carpenter@...cle.com>, paskripkin@...il.com
Cc: Pavel Skripkin <paskripkin@...il.com>, gregkh@...uxfoundation.org,
realwakka@...il.com, linux-staging@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: pi433: prevent uninitialized data from being
printed out
On Mon, Feb 28, 2022 at 09:44:15AM +0300, Dan Carpenter wrote:
> On Sat, Feb 26, 2022 at 04:08:48PM +0300, Pavel Skripkin wrote:
> > > Patch dependency:
> > >
> > > - this patch depends on the following patch to be applied first as
> > > both of them change the same file:
> > > https://lore.kernel.org/lkml/Yhla4a1Clpguoo2h@mail.google.com/
> > > ---
> >
> > You can send all these patches as a patch series with proper order. It will
> > help maintainers to not break the order while applying.
> >
>
> 1) All what Pavel said is true.
Hi Pavel, Hi Dan,
thanks for taking the time to review my patch (and apologies for taking
this long to reply back to you guys).
This patch ended up being merged yesterday so I will be extra careful
for the next patches I send :)
> 3) Greg is going to see that and he is *never* going to click on that
> link. In staging then we do not care about the order of patches.
> Everything is applied in first come first serve basis. If Greg finds
> out that order matters and it is not sent as a patch set then he
> just deletes all your patches and asks you to resend everything
> correctly.
Noted.
Best regards,
Paulo Almeida
Powered by blists - more mailing lists