netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Niklas Cassel <niklas.cassel@linaro.org>
To: Jose Abreu <jose.abreu@synopsys.com>
Cc: netdev@vger.kernel.org, Joao Pinto <joao.pinto@synopsys.com>,
	"David S . Miller" <davem@davemloft.net>,
	Giuseppe Cavallaro <peppe.cavallaro@st.com>,
	Alexandre Torgue <alexandre.torgue@st.com>,
	vinod.koul@linaro.org
Subject: Re: [PATCH net 0/3] net: stmmac: Misc fixes
Date: Tue, 5 Feb 2019 23:05:44 +0100	[thread overview]
Message-ID: <20190205220544.GA25400@centauri.lan> (raw)
In-Reply-To: <cover.1548859967.git.joabreu@synopsys.com>

On Wed, Jan 30, 2019 at 03:54:18PM +0100, Jose Abreu wrote:
> 
> Some misc fixes for stmmac targeting -net.
> 
> Cc: Joao Pinto <jpinto@synopsys.com>
> Cc: David S. Miller <davem@davemloft.net>
> Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>
> Cc: Alexandre Torgue <alexandre.torgue@st.com>
> 
> Jose Abreu (3):
>   net: stmmac: Fallback to Platform Data clock in Watchdog conversion
>   net: stmmac: Send TSO packets always from Queue 0
>   net: stmmac: Disable EEE mode earlier in XMIT callback

Hello Jose,

Thanks for your great work of improving the stmmac driver.

Unfortunately, I'm seeing that a lot of important stmmac fixes
aren't getting backported to stable kernels.


I think that the problem is that a lot of stmmac commit messages do
not clearly indicate what happens if these patches are not included.

See netdev FAQ:

Q: I have created a network patch and I think it should be backported to
   stable.  Should I add a "Cc: stable@vger.kernel.org" like the references
   in the kernel's Documentation/ directory say?

A: No.  See above answer.  In short, if you think it really belongs in
   stable, then ensure you write a decent commit log that describes who
   gets impacted by the bugfix and how it manifests itself, and when the
   bug was introduced.  If you do that properly, then the commit will
   get handled appropriately and most likely get put in the patchworks
   stable queue if it really warrants it.



Could you please tell me what happens if I don't include
"net: stmmac: Disable EEE mode earlier in XMIT callback" ?


likewise if I don't include "net: stmmac: Send TSO packets always from
Queue 0" ?

I assume that I will get a TX timeout if I try to send a TSO packet
from a queue that does not support it?

Also, we already define the TX queues in the snps,mtl-tx-config:
Documentation/devicetree/bindings/net/stmmac.txt

Wouldn't it be possible to add a snps,tso-capable property for each tx
queue node that supports tso?


Kind regards,
Niklas

> 
>  drivers/net/ethernet/stmicro/stmmac/stmmac_ethtool.c | 14 ++++++++++----
>  drivers/net/ethernet/stmicro/stmmac/stmmac_main.c    | 17 +++++++++++++----
>  include/linux/stmmac.h                               |  1 +
>  3 files changed, 24 insertions(+), 8 deletions(-)
> 
> -- 
> 2.7.4
> 

  parent reply	other threads:[~2019-02-05 22:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 14:54 [PATCH net 0/3] net: stmmac: Misc fixes Jose Abreu
2019-01-30 14:54 ` [PATCH net 1/3] net: stmmac: Fallback to Platform Data clock in Watchdog conversion Jose Abreu
2019-01-30 14:54 ` [PATCH net 2/3] net: stmmac: Send TSO packets always from Queue 0 Jose Abreu
2019-01-30 14:54 ` [PATCH net 3/3] net: stmmac: Disable EEE mode earlier in XMIT callback Jose Abreu
2019-01-30 15:17 ` [PATCH net 0/3] net: stmmac: Misc fixes Corentin Labbe
2019-01-31  6:29 ` David Miller
2019-02-05 22:05 ` Niklas Cassel [this message]
2019-02-06  7:37   ` Jose Abreu
  -- strict thread matches above, loose matches on Subject: below --
2025-08-28 10:02 [PATCH net 0/3] net: stmmac: misc fixes Konrad Leszczynski

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=20190205220544.GA25400@centauri.lan \
    --to=niklas.cassel@linaro.org \
    --cc=alexandre.torgue@st.com \
    --cc=davem@davemloft.net \
    --cc=joao.pinto@synopsys.com \
    --cc=jose.abreu@synopsys.com \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=vinod.koul@linaro.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).