From: Haiyang Zhang <haiyangz@microsoft.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sasha Levin <sashal@kernel.org>
Subject: RE: linux-next: Signed-off-by missing for commit in the pci tree
Date: Tue, 10 Sep 2019 13:56:38 +0000 [thread overview]
Message-ID: <DM6PR21MB13375D54A64B2471BBBE62B3CAB60@DM6PR21MB1337.namprd21.prod.outlook.com> (raw)
In-Reply-To: <20190910111737.GA4382@red-moon.cambridge.arm.com>
> -----Original Message-----
> From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> Sent: Tuesday, September 10, 2019 7:18 AM
> To: Haiyang Zhang <haiyangz@microsoft.com>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>; Bjorn Helgaas
> <bhelgaas@google.com>; Linux Next Mailing List <linux-
> next@vger.kernel.org>; Linux Kernel Mailing List <linux-
> kernel@vger.kernel.org>; Sasha Levin <sashal@kernel.org>
> Subject: Re: linux-next: Signed-off-by missing for commit in the pci tree
>
> On Mon, Sep 09, 2019 at 11:10:06PM +0000, Haiyang Zhang wrote:
> >
> >
> > > -----Original Message-----
> > > From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > > Sent: Wednesday, August 21, 2019 5:03 AM
> > > To: Stephen Rothwell <sfr@canb.auug.org.au>
> > > Cc: Bjorn Helgaas <bhelgaas@google.com>; Linux Next Mailing List
> > > <linux- next@vger.kernel.org>; Linux Kernel Mailing List <linux-
> > > kernel@vger.kernel.org>; Sasha Levin <sashal@kernel.org>; Haiyang
> > > Zhang <haiyangz@microsoft.com>
> > > Subject: Re: linux-next: Signed-off-by missing for commit in the pci
> > > tree
> > >
> > > On Wed, Aug 21, 2019 at 07:19:39AM +1000, Stephen Rothwell wrote:
> > > > Hi all,
> > > >
> > > > Commit
> > > >
> > > > c4a29fbba415 ("PCI: hv: Use bytes 4 and 5 from instance ID as
> > > > the PCI
> > > domain numbers")
> > > >
> > > > is missing a Signed-off-by from its committer.
> > > >
> > > > Also, all the tags should be kept together, please.
> > >
> > > Fixed it up in my pci/hv branch, apologies.
> > >
> > > Lorenzo
> >
> > Hi thanks for fixing this, but I found the following commit now has
> > the Subject line and commit message same as a previous patch.
> >
> > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.
> > kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fnext%2Flinux-
> next.git%
> >
> 2Fcommit%2Fdrivers%3Fid%3D87b20a08dcc265959f5c59f18603ea0487fe60
> 9b&
> > ;data=02%7C01%7Chaiyangz%40microsoft.com%7Cb4e2f03b09da4454342
> 108d735e
> >
> 081d0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6370371106
> 95959451&
> >
> amp;sdata=17KZvmvtuHz3f0xKh6MwSOja41VerGTpyAO0f7BF6gY%3D&r
> eserved=
> > 0
> >
> > The correct message for the patch should be the msg below. Any
> > possibility to fix it again? Thanks.
>
> I updated my pci/hv branch and rewrote the commit log, I will ask Bjorn to
> update it so that it shows up in -next.
>
> Lorenzo
Thank you!
next prev parent reply other threads:[~2019-09-10 13:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 21:19 linux-next: Signed-off-by missing for commit in the pci tree Stephen Rothwell
2019-08-21 9:02 ` Lorenzo Pieralisi
2019-09-09 23:10 ` Haiyang Zhang
2019-09-10 11:17 ` Lorenzo Pieralisi
2019-09-10 13:56 ` Haiyang Zhang [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-05 22:05 Stephen Rothwell
2023-10-05 22:23 ` Bjorn Helgaas
2023-09-17 21:57 Stephen Rothwell
2023-02-10 4:38 Stephen Rothwell
2023-02-10 23:28 ` Bjorn Helgaas
2022-05-24 21:07 Stephen Rothwell
2022-05-24 21:43 ` Bjorn Helgaas
2021-02-24 20:21 Stephen Rothwell
2021-02-24 21:31 ` Bjorn Helgaas
2021-01-20 7:25 Stephen Rothwell
2021-01-20 19:26 ` Bjorn Helgaas
2019-02-27 21:01 Stephen Rothwell
2019-02-27 23:51 ` Bjorn Helgaas
2019-02-28 10:03 ` Lorenzo Pieralisi
2019-02-11 23:10 Stephen Rothwell
2019-02-11 23:58 ` Bjorn Helgaas
2018-04-01 1:41 Stephen Rothwell
2018-04-02 0:19 ` Bjorn Helgaas
2018-03-03 4:44 Stephen Rothwell
2018-03-05 14:10 ` Bjorn Helgaas
2018-01-17 20:53 Stephen Rothwell
2018-01-17 21:00 ` Bjorn Helgaas
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=DM6PR21MB13375D54A64B2471BBBE62B3CAB60@DM6PR21MB1337.namprd21.prod.outlook.com \
--to=haiyangz@microsoft.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sashal@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).