From: Alex Elder <elder@linaro.org>
To: Jakub Kicinski <kuba@kernel.org>, Alex Elder <elder@linaro.org>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
andersson@kernel.org, konrad.dybcio@linaro.org,
agross@kernel.org, devicetree@vger.kernel.org,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
elder@kernel.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Simon Horman <simon.horman@corigine.com>
Subject: Re: [PATCH v2] dt-bindings: net: qcom,ipa: add SDX65 compatible
Date: Fri, 17 Mar 2023 07:12:50 -0500 [thread overview]
Message-ID: <b657a2a7-ddf4-d42f-02a9-16f297e9ef07@linaro.org> (raw)
In-Reply-To: <20230316171010.7c51c93c@kernel.org>
On 3/16/23 7:10 PM, Jakub Kicinski wrote:
> On Wed, 15 Mar 2023 14:43:05 -0500 Alex Elder wrote:
>> Add support for SDX65, which uses IPA v5.0.
>>
>> Reviewed-by: Simon Horman <simon.horman@corigine.com>
>> Signed-off-by: Alex Elder <elder@linaro.org>
>> ---
>> v2: Add review tag; base on linux-next/master; drop "net-next" in subject
>>
>> It is my intention to have this patch be taken via the Qualcomm
>> repository (not net-next).
>
> That's a bit unusual, no strong feelings but why is that?
> Bindings usually go with the code, ipa is a networking thing, right?
I'm sorry, yes, there is no reason the bindings update
should be taken through the Qualcomm tree.
This is a trivial patch. This version (2) is based on
linux-next/master but it can be cleanly cherry-picked
onto net-next/master.
Please accept this patch via net-next, and if you want
me to send an updated version, please say so.
I'm very sorry for the confusion here. For some reason
this has been a rough week with little patches for me.
-Alex
next prev parent reply other threads:[~2023-03-17 12:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 19:43 Alex Elder
2023-03-17 0:10 ` Jakub Kicinski
2023-03-17 12:12 ` Alex Elder [this message]
2023-03-18 5:40 ` patchwork-bot+netdevbpf
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=b657a2a7-ddf4-d42f-02a9-16f297e9ef07@linaro.org \
--to=elder@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=robh+dt@kernel.org \
--cc=simon.horman@corigine.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
all inboxes | Powered by JetHome®