lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZoJg_k2En6bqQzA4@ryzen.lan>
Date: Mon, 1 Jul 2024 09:55:42 +0200
From: Niklas Cassel <cassel@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Krzysztof WilczyƄski <kw@...ux.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the pci tree

On Mon, Jul 01, 2024 at 09:13:20AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   aaf840725904 ("PCI: dw-rockchip: Depend on PCI_ENDPOINT if building endpoint mode support")
> 
> Fixes tag
> 
>   Fixes: 9b2ba393b3a6 ("PCI: dw-rockchip: Add endpoint mode support")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: 728538f5e806 ("PCI: dw-rockchip: Add endpoint mode support")


Hello Stephen,

yes, that is correct.
The branch was rebased so the SHA1 changed.

Perhaps the maintainers could update the Fixes tag.

(Personally, I would just squash the small fix with the commit that it fixes.)


Kind regards,
Niklas

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ