From: Rohan G Thomas <rohan.g.thomas@intel.com>
To: kuba@kernel.org
Cc: alexandre.torgue@foss.st.com, conor+dt@kernel.org,
conor.dooley@microchip.com, davem@davemloft.net,
devicetree@vger.kernel.org, edumazet@google.com,
fancer.lancer@gmail.com, joabreu@synopsys.com,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
mcoquelin.stm32@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, peppe.cavallaro@st.com, robh+dt@kernel.org,
rohan.g.thomas@intel.com
Subject: Re: [PATCH net-next v5 1/2] dt-bindings: net: snps,dwmac: Tx queues with coe
Date: Wed, 23 Aug 2023 13:45:37 +0800 [thread overview]
Message-ID: <20230823054537.23328-1-rohan.g.thomas@intel.com> (raw)
In-Reply-To: <20230822171525.692bd2df@kernel.org>
On Sat, 19 Aug 2023 10:31:31 +0800 Rohan G Thomas wrote:
>> + snps,tx-queues-with-coe:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description: number of TX queues that support TX checksum
>> + offloading
>
>Is it going to be obvious that if not present all queues support checksum offload? I think we should document the default.
Agreed. Will add this in the next version.
BR,
Rohan
next prev parent reply other threads:[~2023-08-23 5:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 2:31 [PATCH net-next v5 0/2] net: stmmac: Tx coe sw fallback Rohan G Thomas
2023-08-19 2:31 ` [PATCH net-next v5 1/2] dt-bindings: net: snps,dwmac: Tx queues with coe Rohan G Thomas
2023-08-21 12:15 ` Serge Semin
2023-08-23 0:15 ` Jakub Kicinski
2023-08-23 5:45 ` Rohan G Thomas [this message]
2023-08-23 10:00 ` Serge Semin
2023-08-23 17:10 ` Rohan G Thomas
2023-08-27 0:18 ` Serge Semin
2023-08-19 2:31 ` [PATCH net-next v5 2/2] net: stmmac: Tx coe sw fallback Rohan G Thomas
2023-08-21 12:15 ` Serge Semin
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=20230823054537.23328-1-rohan.g.thomas@intel.com \
--to=rohan.g.thomas@intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=fancer.lancer@gmail.com \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).