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
| ||
|
Message-ID: <20250610144046.1deba9f3@kernel.org> Date: Tue, 10 Jun 2025 14:40:46 -0700 From: Jakub Kicinski <kuba@...nel.org> To: Shradha Gupta <shradhagupta@...ux.microsoft.com> Cc: linux-hyperv@...r.kernel.org, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org, Nipun Gupta <nipun.gupta@....com>, Yury Norov <yury.norov@...il.com>, Jason Gunthorpe <jgg@...pe.ca>, Jonathan Cameron <Jonathan.Cameron@...ei.com>, Anna-Maria Behnsen <anna-maria@...utronix.de>, Kevin Tian <kevin.tian@...el.com>, Long Li <longli@...rosoft.com>, Thomas Gleixner <tglx@...utronix.de>, Bjorn Helgaas <bhelgaas@...gle.com>, Rob Herring <robh@...nel.org>, Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>, Krzysztof Wilczy�~Dski <kw@...ux.com>, Lorenzo Pieralisi <lpieralisi@...nel.org>, Dexuan Cui <decui@...rosoft.com>, Wei Liu <wei.liu@...nel.org>, Haiyang Zhang <haiyangz@...rosoft.com>, "K. Y. Srinivasan" <kys@...rosoft.com>, Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Konstantin Taranov <kotaranov@...rosoft.com>, Simon Horman <horms@...nel.org>, Leon Romanovsky <leon@...nel.org>, Maxim Levitsky <mlevitsk@...hat.com>, Erni Sri Satya Vennela <ernis@...ux.microsoft.com>, Peter Zijlstra <peterz@...radead.org>, netdev@...r.kernel.org, linux-rdma@...r.kernel.org, Paul Rosswurm <paulros@...rosoft.com>, Shradha Gupta <shradhagupta@...rosoft.com> Subject: Re: [PATCH v5 0/5] Allow dyn MSI-X vector allocation of MANA On Mon, 9 Jun 2025 06:48:21 -0700 Shradha Gupta wrote: > Since this patchset has patches from PCI and net tree, I am not entirely > sure what should be the target tree. Any suggestions/recommendations on > the same are welcomed. Could you put these on a branch based on v6.16-rc1 ? That why if someone else needs them before the next merge window they can pull that branch. The patches look fine to me.
Powered by blists - more mailing lists