From: David Miller <davem@davemloft.net>
To: leedom@chelsio.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] cxgb3: new code to deal with adapter parity errors
Date: Fri, 03 Sep 2010 10:04:38 -0700 (PDT) [thread overview]
Message-ID: <20100903.100438.123990943.davem@davemloft.net> (raw)
In-Reply-To: <241D2F16-4F92-48DD-A904-832771B2F4B4@chelsio.com>
From: Casey Leedom <leedom@chelsio.com>
Date: Thu, 2 Sep 2010 16:04:28 -0700
> These patches implement code to detect and recover from adapter parity errors.
>
> Two of the following four patches (2/4 and 3/4) were actually
> implemented by Dimitris Michailidis just before he headed off for
> vacation. I've indicated that via a "Signed-off-by" by-line for
> him as well as one for me which I _think_ is the right way to do
> this. The other two patches (1/4 and 4/4) were implemented by me
> so I've only included a "Signed-off-by" for me on those. If I've
> done anything incorrectly please reject the patches and tell me
> how to correct them. Thanks!
All applied, thanks Casey.
prev parent reply other threads:[~2010-09-03 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 23:04 [PATCH net-next 0/4] cxgb3: new code to deal with adapter parity errors Casey Leedom
2010-09-02 23:07 ` [PATCH net-next 1/4] cxgb3: Add register bit definition for Fatal Parity Error Casey Leedom
2010-09-02 23:07 ` [PATCH net-next 2/4] cxgb3: Set FATALPERREN Casey Leedom
2010-09-02 23:07 ` [PATCH net-next 3/4] cxgb3: Leave interrupts for fatal errors asserted in common code Casey Leedom
2010-09-02 23:07 ` [PATCH net-next 4/4] cxgb3: Avoid flush_workqueue() deadlock Casey Leedom
2010-09-03 17:04 ` 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=20100903.100438.123990943.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=leedom@chelsio.com \
--cc=netdev@vger.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).