From: Paolo Abeni <pabeni@redhat.com>
To: Yijie Yang <quic_yijiyang@quicinc.com>,
Vinod Koul <vkoul@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Jose Abreu <joabreu@synopsys.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, quic_tingweiz@quicinc.com,
quic_aiquny@quicinc.com, quic_tengfan@quicinc.com,
quic_jiegan@quicinc.com, quic_jingyw@quicinc.com,
quic_jsuraj@quicinc.com
Subject: Re: [PATCH 0/3] Add standalone ethernet MAC entries for qcs615
Date: Tue, 19 Nov 2024 12:18:00 +0100 [thread overview]
Message-ID: <3cfc2e90-c9b4-425d-80f4-ddace9aff021@redhat.com> (raw)
In-Reply-To: <20241118-schema-v1-0-11b7c1583c0c@quicinc.com>
On 11/18/24 07:16, Yijie Yang wrote:
> Add separate EMAC entries for qcs615 since its core version is 2.3.1,
> compared to sm8150's 2.1.2.
>
> Signed-off-by: Yijie Yang <quic_yijiyang@quicinc.com>
## Form letter - net-next-closed
The merge window for v6.13 has begun and net-next is closed for new
drivers, features, code refactoring and optimizations. We are currently
accepting bug fixes only.
Please repost when net-next reopens after Dec 2nd.
RFC patches sent for review only are welcome at any time.
See:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
next prev parent reply other threads:[~2024-11-19 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 6:16 [PATCH 0/3] Add standalone ethernet MAC entries for qcs615 Yijie Yang
2024-11-18 6:16 ` [PATCH 1/3] dt-bindings: net: qcom,ethqos: revise description " Yijie Yang
2024-11-19 17:41 ` Rob Herring
2024-11-22 1:17 ` Yijie Yang
2024-11-18 6:16 ` [PATCH 2/3] dt-bindings: net: snps,dwmac: add " Yijie Yang
2024-11-18 6:16 ` [PATCH 3/3] net: stmmac: dwmac-qcom-ethqos: add support for EMAC on qcs615 platforms Yijie Yang
2024-11-19 11:18 ` Paolo Abeni [this message]
2024-11-22 1:20 ` [PATCH 0/3] Add standalone ethernet MAC entries for qcs615 Yijie Yang
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=3cfc2e90-c9b4-425d-80f4-ddace9aff021@redhat.com \
--to=pabeni@redhat.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhupesh.sharma@linaro.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=quic_aiquny@quicinc.com \
--cc=quic_jiegan@quicinc.com \
--cc=quic_jingyw@quicinc.com \
--cc=quic_jsuraj@quicinc.com \
--cc=quic_tengfan@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_yijiyang@quicinc.com \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
/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