From: David Decotigny <decot@google.com>
To: David Miller <davem@davemloft.net>
Cc: Joe Perches <joe@perches.com>,
szymon@janc.net.pl, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-net-upstream@google.com,
snanda@google.com
Subject: Re: [PATCH] forcedeth: new ethtool stat "tx_timeout" to account for tx_timeouts
Date: Wed, 18 May 2011 14:20:21 -0700 [thread overview]
Message-ID: <BANLkTimNvuB5HtOKfAc7rf5wF2QeC3xdXw@mail.gmail.com> (raw)
In-Reply-To: <20110518.171416.1780927258138770742.davem@davemloft.net>
Hi David,
They should be independent and applicable in any order, except for the
two 'PATCH x/2' which have to go together.
FYI, here is the order in which I'm applying them:
1/ forcedeth: Improve stats counters
2/ forcedeth: new ethtool stat "tx_timeout" to account for tx_timeouts
3/ [PATCH 1/2] forcedeth: make module parameters readable in /sys/module
4/ [PATCH 2/2] forcedeth: allow to silence tx_timeout debug messages
5/ forcedeth: Acknowledge only interrupts that are being processed
6/ forcedeth: Add messages to indicate using MSI or MSI-X
7/ forcedeth: Fix a race during rmmod of forcedeth
Sorry for that.
Regards,
--
David Decotigny
On Wed, May 18, 2011 at 2:14 PM, David Miller <davem@davemloft.net> wrote:
>
> When submitting multiple patches in a patch set, NUMBER THEM.
>
> Otherwise there is no unambiguous way to figure out what order
> I should apply these patches.
>
next prev parent reply other threads:[~2011-05-18 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 21:09 [PATCH] forcedeth: Improve stats counters David Decotigny
2011-05-18 21:09 ` [PATCH] forcedeth: new ethtool stat "tx_timeout" to account for tx_timeouts David Decotigny
2011-05-18 21:14 ` David Miller
2011-05-18 21:20 ` David Decotigny [this message]
2011-05-18 21:26 ` David Miller
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=BANLkTimNvuB5HtOKfAc7rf5wF2QeC3xdXw@mail.gmail.com \
--to=decot@google.com \
--cc=davem@davemloft.net \
--cc=joe@perches.com \
--cc=kernel-net-upstream@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=snanda@google.com \
--cc=szymon@janc.net.pl \
/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).