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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a7720a091ea02a6bbaa88c7311d7a642f9c7fdff.camel@redhat.com>
Date: Fri, 28 Feb 2025 10:26:24 +0100
From: Philipp Stanner <pstanner@...hat.com>
To: Jakub Kicinski <kuba@...nel.org>, Philipp Stanner <phasta@...nel.org>
Cc: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
 <davem@...emloft.net>,  Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
 <pabeni@...hat.com>, Maxime Coquelin <mcoquelin.stm32@...il.com>, Alexandre
 Torgue <alexandre.torgue@...s.st.com>,  Huacai Chen
 <chenhuacai@...nel.org>, Yanteng Si <si.yanteng@...ux.dev>, Yinggang Gu
 <guyinggang@...ngson.cn>,  Feiyang Chen <chenfeiyang@...ngson.cn>, Jiaxun
 Yang <jiaxun.yang@...goat.com>, Qing Zhang <zhangqing@...ngson.cn>,
 netdev@...r.kernel.org,  linux-stm32@...md-mailman.stormreply.com,
 linux-arm-kernel@...ts.infradead.org,  linux-kernel@...r.kernel.org,
 stable@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,  Henry Chen
 <chenx97@...c.io>
Subject: Re: [PATCH net-next v4 1/4] stmmac: loongson: Pass correct arg to
 PCI function

On Thu, 2025-02-27 at 18:35 -0800, Jakub Kicinski wrote:
> On Wed, 26 Feb 2025 09:52:05 +0100 Philipp Stanner wrote:
> > pcim_iomap_regions() should receive the driver's name as its third
> > parameter, not the PCI device's name.
> > 
> > Define the driver name with a macro and use it at the appropriate
> > places, including pcim_iomap_regions().
> > 
> > Cc: stable@...r.kernel.org # v5.14+
> > Fixes: 30bba69d7db4 ("stmmac: pci: Add dwmac support for Loongson")
> 
> Since you sent this as a fix (which.. yea.. I guess.. why not..)
> I'll apply it to the fixes tree. But then the other patches have 
> to wait and be reposted next Thu. The fixes are merged with net-next
> every Thu, but since this series was tagged as net-next I missed
> it in today's cross merge :(
> 

Oh OK, I see – I'm not very familiar with the net subsystem process. So
far I always had it like this: fire everything into Linus's master and
Greg & Sasha then pick those with Fixes tags into the stable trees
automatically :)

Anyways, I interpret your message so that this series is done and I
don't have to do anything about it anymore. Correct me if I'm wrong.


Thanks
P.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ