linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>, paskripkin@gmail.com
Cc: Pavel Skripkin <paskripkin@gmail.com>,
	gregkh@linuxfoundation.org, realwakka@gmail.com,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: pi433: prevent uninitialized data from being printed out
Date: Wed, 2 Mar 2022 22:02:46 +1300	[thread overview]
Message-ID: <Yh8ytrK7EJjYbrHF@mail.google.com> (raw)
In-Reply-To: <20220228064415.GB2794@kadam>

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

      reply	other threads:[~2022-03-02  9:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26  4:25 [PATCH] staging: pi433: prevent uninitialized data from being printed out Paulo Miguel Almeida
2022-02-26 13:08 ` Pavel Skripkin
2022-02-28  6:44   ` Dan Carpenter
2022-03-02  9:02     ` Paulo Miguel Almeida [this message]

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=Yh8ytrK7EJjYbrHF@mail.google.com \
    --to=paulo.miguel.almeida.rodenas@gmail.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=paskripkin@gmail.com \
    --cc=realwakka@gmail.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).