From: Bjorn Helgaas <helgaas@kernel.org>
To: "Alexey V. Vissarionov" <gremlin@altlinux.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the pci tree
Date: Wed, 18 Jan 2023 11:06:38 -0600 [thread overview]
Message-ID: <20230118170638.GA225976@bhelgaas> (raw)
In-Reply-To: <20230116032354.GA8107@altlinux.org>
On Mon, Jan 16, 2023 at 06:23:55AM +0300, Alexey V. Vissarionov wrote:
> On 2023-01-16 08:14:25 +1100, Stephen Rothwell wrote:
> > In commit
> > 58d4c63d0a27 ("PCI/IOV: Enlarge virtfn sysfs name buffer")
> > Fixes tag
> > Fixes: dd7cc44d0 ("PCI: add SR-IOV API for Physical Function driver")
> > has these problem(s):
> > - SHA1 should be at least 12 digits long
>
> Full SHA1 is dd7cc44d0bcec5e9c42fe52e88dc254ae62eac8d
> First 12 digits would obviously be dd7cc44d0bce
I fixed it locally for you, so no need to repost for this.
Bjorn
next prev parent reply other threads:[~2023-01-18 17:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 21:14 linux-next: Fixes tag needs some work in the pci tree Stephen Rothwell
2023-01-16 3:23 ` Alexey V. Vissarionov
2023-01-18 17:06 ` Bjorn Helgaas [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-22 9:55 Stephen Rothwell
2020-11-22 15:13 ` Bjorn Helgaas
2020-07-22 0:33 Stephen Rothwell
2020-03-30 20:38 Stephen Rothwell
2020-03-30 20:53 ` Bjorn Helgaas
2020-03-31 3:14 ` Lukas Wunner
2020-03-31 3:32 ` Lukas Wunner
2020-03-31 15:32 ` Bjorn Helgaas
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=20230118170638.GA225976@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gremlin@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.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).