From: Jakub Kicinski <kuba@kernel.org>
To: Rohan G Thomas <rohan.g.thomas@intel.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Serge Semin <fancer.lancer@gmail.com>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH net-next v5 1/2] dt-bindings: net: snps,dwmac: Tx queues with coe
Date: Tue, 22 Aug 2023 17:15:25 -0700 [thread overview]
Message-ID: <20230822171525.692bd2df@kernel.org> (raw)
In-Reply-To: <20230819023132.23082-2-rohan.g.thomas@intel.com>
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.
--
pw-bot: cr
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Rohan G Thomas <rohan.g.thomas@intel.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Serge Semin <fancer.lancer@gmail.com>,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH net-next v5 1/2] dt-bindings: net: snps,dwmac: Tx queues with coe
Date: Tue, 22 Aug 2023 17:15:25 -0700 [thread overview]
Message-ID: <20230822171525.692bd2df@kernel.org> (raw)
In-Reply-To: <20230819023132.23082-2-rohan.g.thomas@intel.com>
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.
--
pw-bot: cr
next prev parent reply other threads:[~2023-08-23 0:16 UTC|newest]
Thread overview: 20+ 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 ` 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-19 2:31 ` Rohan G Thomas
2023-08-21 12:15 ` Serge Semin
2023-08-21 12:15 ` Serge Semin
2023-08-23 0:15 ` Jakub Kicinski [this message]
2023-08-23 0:15 ` Jakub Kicinski
2023-08-23 5:45 ` Rohan G Thomas
2023-08-23 5:45 ` Rohan G Thomas
2023-08-23 10:00 ` Serge Semin
2023-08-23 10:00 ` Serge Semin
2023-08-23 17:10 ` Rohan G Thomas
2023-08-23 17:10 ` Rohan G Thomas
2023-08-27 0:18 ` Serge Semin
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-19 2:31 ` Rohan G Thomas
2023-08-21 12:15 ` Serge Semin
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=20230822171525.692bd2df@kernel.org \
--to=kuba@kernel.org \
--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=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 \
--cc=rohan.g.thomas@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.