From: Bjorn Helgaas <helgaas@kernel•org>
To: Mark Brown <broonie@kernel•org>
Cc: "Bjorn Helgaas" <bhelgaas@google•com>,
"Lorenzo Pieralisi" <lpieralisi@kernel•org>,
"Krzysztof Wilczyński" <kwilczynski@kernel•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
"Manivannan Sadhasivam" <mani@kernel•org>,
"Aksh Garg" <a-garg7@ti•com>, "Koichiro Den" <den@valinux•co.jp>
Subject: Re: Fixes tags could use some work in the pci tree
Date: Tue, 3 Feb 2026 17:13:52 -0600 [thread overview]
Message-ID: <20260203231352.GA195886@bhelgaas> (raw)
In-Reply-To: <484d687e-4ce1-442e-b8c1-9299631a7fe1@sirena.org.uk>
[+cc Mani (should be cc'd for all PCI emails like this), Aksh, Koichiro]
On Mon, Feb 02, 2026 at 11:48:44AM +0000, Mark Brown wrote:
> In commit
>
> b386d03d6aad2 ("PCI: dwc: ep: Add per-PF BAR and inbound ATU mapping support")
>
> Fixes tag
>
> Fixes: cfbc98dbf44d ("PCI: dwc: ep: Support BAR subrange inbound mapping via Address Match Mode iATU")
>
> has these problem(s):
>
> - Target SHA1 does not exist
Thanks, Mark.
cfbc98dbf44d is now cc839bef7727 ("PCI: dwc: ep: Support BAR subrange
inbound mapping via Address Match Mode iATU") (same patch, different
SHA1) because I rewrapped a comment in the patch.
I updated the b386d03d6aad2 commit log to mention cc839bef7727
instead.
Both b386d03d6aad2 and cc839bef7727 are queued on pci/controller/dwc
for v6.20. Ideally, I think they would be reordered so we don't add
something that's broken, and then have to fix it in the same merge
window.
But I guess it should be fixed enough to avoid this warning.
Bjorn
next prev parent reply other threads:[~2026-02-03 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 11:48 Fixes tags could use some work in the pci tree Mark Brown
2026-02-03 23:13 ` Bjorn Helgaas [this message]
2026-02-04 11:58 ` Mark Brown
2026-02-04 12:24 ` Manivannan Sadhasivam
2026-02-04 12:42 ` Mark Brown
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=20260203231352.GA195886@bhelgaas \
--to=helgaas@kernel$(echo .)org \
--cc=a-garg7@ti$(echo .)com \
--cc=bhelgaas@google$(echo .)com \
--cc=broonie@kernel$(echo .)org \
--cc=den@valinux$(echo .)co.jp \
--cc=kwilczynski@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lpieralisi@kernel$(echo .)org \
--cc=mani@kernel$(echo .)org \
/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