From: David Miller <davem@davemloft.net>
To: Ramkrishna.Vepa@neterion.com
Cc: roel.kluin@gmail.com, netdev@vger.kernel.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] S2io: two branches the same in wait_for_cmd_complete()
Date: Tue, 19 Jan 2010 01:59:59 -0800 (PST) [thread overview]
Message-ID: <20100119.015959.104877543.davem@davemloft.net> (raw)
In-Reply-To: <78C9135A3D2ECE4B8162EBDCE82CAD77061418BF@nekter>
From: "Ramkrishna Vepa" <Ramkrishna.Vepa@neterion.com>
Date: Mon, 18 Jan 2010 02:20:06 -0500
> Thanks for catching this bug. The fix should be as follows -
This doesn't apply to net-2.6, and I'd need your signoff too.
Please fix this up and resubmit, thanks.
prev parent reply other threads:[~2010-01-19 9:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 15:10 [PATCH] S2io: two branches the same in wait_for_cmd_complete() Roel Kluin
2010-01-18 3:13 ` David Miller
2010-01-18 3:58 ` Joe Perches
2010-01-18 7:20 ` Ramkrishna Vepa
2010-01-19 9:59 ` 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=20100119.015959.104877543.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ramkrishna.Vepa@neterion.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roel.kluin@gmail.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).