From: Lukas Wunner <lukas@wunner•de>
To: Bjorn Helgaas <bjorn.helgaas@gmail•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the pci tree
Date: Tue, 31 Mar 2020 05:32:32 +0200 [thread overview]
Message-ID: <20200331033232.27ifep6igs45xv75@wunner.de> (raw)
In-Reply-To: <20200331031458.x6y73bisl7cj3gpd@wunner.de>
On Tue, Mar 31, 2020 at 05:14:58AM +0200, Lukas Wunner wrote:
> On Mon, Mar 30, 2020 at 03:53:29PM -0500, Bjorn Helgaas wrote:
> > On Mon, Mar 30, 2020 at 3:39 PM Stephen Rothwell <sfr@canb•auug.org.au> wrote> > In commit
> > >
> > > fb3ffadca55a ("PCI: pciehp: Fix indefinite wait on sysfs requests")
> > >
> > > Fixes tag
> > >
> > > Fixes: 54ecb8f7028c ("PCI: pciehp: Avoid returning prematurely from sysfs requests")
> > >
> > > has these problem(s):
> > >
> > > - Subject does not match target commit subject
> > > Just use
> > > git log -1 --format='Fixes: %h ("%s")'
> > >
> > > Did you mean
> > >
> > > (probably not :-))
> > > Fixes: 54ecb8f7028c ("Linux 5.4-rc1")
> > >
> > > or
> > >
> > > Fixes: 157c1062fcd8 ("PCI: pciehp: Avoid returning prematurely from sysfs requests")
> >
> > Fixed, thanks!
>
> Ugh, sorry about that.
>
> In case you're not aware, it's only fixed on your next branch,
> not on the pci/hotplug branch.
Also, the incorrect commit hash is repeated further up in the commit
message: "This flag, which was introduced by commit 54ecb8f7028c"
Again, sorry, I don't really understand how this happened.
Thanks,
Lukas
next prev parent reply other threads:[~2020-03-31 3:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 20:38 linux-next: Fixes tag needs some work in the pci tree Stephen Rothwell
2020-03-30 20:53 ` Bjorn Helgaas
2020-03-31 3:14 ` Lukas Wunner
2020-03-31 3:32 ` Lukas Wunner [this message]
2020-03-31 15:32 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 21:08 Stephen Rothwell
2024-10-24 21:10 ` Stephen Rothwell
2024-10-24 21:21 ` Mario Limonciello
2024-06-30 23:13 Stephen Rothwell
2024-07-01 7:55 ` Niklas Cassel
2024-07-01 20:18 ` Krzysztof Wilczyński
2023-01-15 21:14 Stephen Rothwell
2023-01-16 3:23 ` Alexey V. Vissarionov
2023-01-18 17:06 ` Bjorn Helgaas
2020-11-22 9:55 Stephen Rothwell
2020-11-22 15:13 ` Bjorn Helgaas
2020-07-22 0:33 Stephen Rothwell
2019-06-22 13:40 Stephen Rothwell
2019-06-26 10:00 ` Lorenzo Pieralisi
2019-06-26 14:51 ` Bharat Kumar Gogada
2019-02-12 23:03 Stephen Rothwell
2019-02-13 9:55 ` Lorenzo Pieralisi
2019-02-13 14:31 ` Bjorn Helgaas
2019-02-13 20:09 ` Stephen Rothwell
2019-02-13 20:19 ` Bjorn Helgaas
2019-02-13 21:17 ` Stephen Rothwell
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=20200331033232.27ifep6igs45xv75@wunner.de \
--to=lukas@wunner$(echo .)de \
--cc=bjorn.helgaas@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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