linux-kernel - Re: [PATCH net-next v4 00/14] Add PPE driver for Qualcomm IPQ9574 SoC

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: <20250515072457.55902bfd@kernel.org>
Date: Thu, 15 May 2025 07:24:57 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Luo Jie <quic_luoj@...cinc.com>
Cc: Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
 <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
 <pabeni@...hat.com>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski
 <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Lei Wei
 <quic_leiwei@...cinc.com>, Suruchi Agarwal <quic_suruchia@...cinc.com>,
 Pavithra R <quic_pavir@...cinc.com>, Simon Horman <horms@...nel.org>,
 Jonathan Corbet <corbet@....net>, Kees Cook <kees@...nel.org>, "Gustavo A.
 R. Silva" <gustavoars@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
 <linux-arm-msm@...r.kernel.org>, <netdev@...r.kernel.org>,
 <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
 <linux-doc@...r.kernel.org>, <linux-hardening@...r.kernel.org>,
 <quic_kkumarcs@...cinc.com>, <quic_linchen@...cinc.com>,
 <srinivas.kandagatla@...aro.org>, <bartosz.golaszewski@...aro.org>,
 <john@...ozen.org>
Subject: Re: [PATCH net-next v4 00/14] Add PPE driver for Qualcomm IPQ9574
 SoC

On Thu, 15 May 2025 22:19:11 +0800 Luo Jie wrote:
> However, from the patchwork result as below, it seems the dependent
> patch series (for FIELD_MODIFY() macro) did not get picked to validate
> the PPE driver patch series together. This dependency is mentioned in
> the cover letter. Could you advise what could be wrong here, which is
> preventing the dependent patch to be picked up? Thanks.

Please try to read more about kernel development process.
These patches are not in Linus's tree or the networking tree.
If you want to use them you have to wait with your submission
until after the next merge window.