From: Simon Horman <horms@kernel.org>
To: Esteban Urrutia <esteuwu@proton.me>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Alex Elder <elder@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Nazar Kompanets <xlie7669@gmail.com>,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/3] SM8450 IPA support
Date: Wed, 9 Sep 2026 19:12:01 +0100 [thread overview]
Message-ID: <20260909181201.GL40544@horms.kernel.org> (raw)
In-Reply-To: <fa9794e3-d79e-4d77-8166-492d992154b4@proton.me>
On Wed, Sep 09, 2026 at 03:12:51AM +0000, Esteban Urrutia wrote:
> On 9/9/26 12:10 AM, Esteban Urrutia wrote:
> > This series has been tested on the following SoCs:
> > - SM7475
> > - SM8450
> > - SM8475
> > In these the modem works as expected and no crashes occur.
>
> I forgot to mention that this series depends on the following patch:
> https://lore.kernel.org/all/20260909-ipa-modem-drop-v1-1-0c9664f09c4a@proton.me/
Our CI isn't smart enough to pick up dependencies.
So you'll need to repost once that patch is present in net-next.
As is, patch 2/3 fails to build.
Also, I think the patch-set needs to be split up somehow
so the networking portions can be accepted into net-next
while the other patches go via a different subsystem.
For the net-next portion, please set the target tree in the subject
like this:
Subject: [PATCH v3 net-next] ...
For more information on the Netdev development process, please see:
https://docs.kernel.org/process/maintainer-netdev.html
--
pw-bot: changes-requested
prev parent reply other threads:[~2026-09-09 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 3:10 [PATCH v2 0/3] SM8450 IPA support Esteban Urrutia
2026-09-09 3:11 ` [PATCH v2 1/3] dt-bindings: net: qcom,ipa: Add SM8450 compatible Esteban Urrutia
2026-09-09 3:11 ` [PATCH v2 2/3] net: ipa: Add IPA v5.1 configuration data Esteban Urrutia
2026-09-09 3:11 ` [PATCH v2 3/3] arm64: dts: qcom: sm8450: Add IPA node Esteban Urrutia
2026-09-09 19:06 ` Dmitry Baryshkov
2026-09-09 21:04 ` Esteban Urrutia
2026-09-09 3:12 ` [PATCH v2 0/3] SM8450 IPA support Esteban Urrutia
2026-09-09 18:12 ` Simon Horman [this message]
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=20260909181201.GL40544@horms.kernel.org \
--to=horms@kernel.org \
--cc=andersson@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=esteuwu@proton.me \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=xlie7669@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).