From: David Miller <davem@davemloft.net>
To: prashant@broadcom.com
Cc: netdev@vger.kernel.org, mchan@broadcom.com
Subject: Re: [PATCH net]tg3: Modify tg3_tso_bug() to handle multiple TX rings
Date: Tue, 05 Aug 2014 16:49:40 -0700 (PDT) [thread overview]
Message-ID: <20140805.164940.1613258811508714514.davem@davemloft.net> (raw)
In-Reply-To: <1407279722-1485-1-git-send-email-prashant@broadcom.com>
From: Prashant Sreedharan <prashant@broadcom.com>
Date: Tue, 5 Aug 2014 16:02:02 -0700
> tg3_tso_bug() was originally designed to handle only HW TX ring 0, Commit
> d3f6f3a1d818410c17445bce4f4caab52eb102f1 ("tg3: Prevent page allocation failure
> during TSO workaround") changed the driver logic to use tg3_tso_bug() for all
> HW TX rings that are enabled. This patch fixes the regression by modifying
> tg3_tso_bug() to handle multiple HW TX rings.
>
> Signed-off-by: Prashant Sreedharan <prashant@broadcom.com>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2014-08-05 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 23:02 [PATCH net]tg3: Modify tg3_tso_bug() to handle multiple TX rings Prashant Sreedharan
2014-08-05 23:49 ` David Miller [this message]
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=20140805.164940.1613258811508714514.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=prashant@broadcom.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;
as well as URLs for NNTP newsgroup(s).