linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
	cgel.zte@gmail.com, robh@kernel.org, kw@linux.com,
	bhelgaas@google.com, rjui@broadcom.com, sbranden@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	ye xingchen <ye.xingchen@zte.com.cn>,
	Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] PCI: iproc: Remove the unneeded result variable
Date: Tue, 27 Sep 2022 14:38:11 +0200	[thread overview]
Message-ID: <YzLus6orb+t0yyD+@kroah.com> (raw)
In-Reply-To: <YzLnmGiU7qcWkeH2@lpieralisi>

On Tue, Sep 27, 2022 at 02:07:52PM +0200, Lorenzo Pieralisi wrote:
> [+Greg]
> 
> On Tue, Sep 06, 2022 at 04:25:20PM -0500, Bjorn Helgaas wrote:
> > On Tue, Sep 06, 2022 at 07:16:36AM +0000, cgel.zte@gmail.com wrote:
> > > From: ye xingchen <ye.xingchen@zte.com.cn>
> > > 
> > > Return the value iproc_pcie_setup_ib() directly instead of storing it in
> > > another redundant variable.
> > > 
> > > Reported-by: Zeal Robot <zealci@zte.com.cn>
> > > Signed-off-by: ye xingchen <ye.xingchen@zte.com.cn>
> > 
> > This patch itself is fine, but was posted by cgel.zte@gmail.com, not by
> > "ye xingchen <ye.xingchen@zte.com.cn>", so it needs another signoff
> > and full name so the chain is complete.  For more details see:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=v5.18#n363
> 
> Greg, Bjorn,
> 
> I believe that appending a SoB like this myself is fine:
> 
> Signed-off-by: CGEL ZTE <cgel.zte@gmail.com>
> 
> It is a SOB already in kernel commit logs - I assume
> that's the right thing to do in this case, please
> let me know if it isn't and what should we do instead.

Please just drop all patches submitted by this email address and from
zte.com.cn at this point in time as we are unable to actually determine
that they are coming from the correct developers.

Also there's no feedback from them at all, which means no one is
actually reading the email it is being purported to be sent from, which
means it should be dropped no matter what anyway.

thanks,

greg k-h

      reply	other threads:[~2022-09-27 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  7:16 [PATCH linux-next] PCI: iproc: Remove the unneeded result variable cgel.zte
2022-09-06 16:54 ` Florian Fainelli
2022-09-06 21:25 ` Bjorn Helgaas
2022-09-06 21:27   ` Scott Branden
2022-09-06 21:37     ` Florian Fainelli
2022-09-07  3:10   ` [PATCH linux-next] cgel.zte
2022-09-27 12:07   ` [PATCH linux-next] PCI: iproc: Remove the unneeded result variable Lorenzo Pieralisi
2022-09-27 12:38     ` Greg KH [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=YzLus6orb+t0yyD+@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=cgel.zte@gmail.com \
    --cc=helgaas@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=rjui@broadcom.com \
    --cc=robh@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=ye.xingchen@zte.com.cn \
    --cc=zealci@zte.com.cn \
    /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).