From: David Miller <davem@davemloft.net>
To: eilong@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 18/34]bnx2x: Reset HW before use
Date: Thu, 22 Jan 2009 13:45:29 -0800 (PST) [thread overview]
Message-ID: <20090122.134529.216388103.davem@davemloft.net> (raw)
In-Reply-To: <1232631443.29087.27.camel@lb-tlvb-eliezer>
From: "Eilon Greenstein" <eilong@broadcom.com>
Date: Thu, 22 Jan 2009 15:37:23 +0200
> For some reason, patches 18-21 did not make it to the git (even though
> you responded with "Applied" to those 4). I guess that this is what
> happen when I send too many patches...
>
> I'm re-sending those 4 after slightly adjusting the lines so it will be
> easier to accept with the current net-2.6 (but without any real change
> from the previous submit).
Sorry about that, I don't know how those got lost.
All applied, thanks a lot for catching this.
prev parent reply other threads:[~2009-01-22 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 16:43 [PATCH 18/34]bnx2x: Reset HW before use Eilon Greenstein
2009-01-18 7:17 ` David Miller
2009-01-22 13:37 ` Eilon Greenstein
2009-01-22 21:45 ` 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=20090122.134529.216388103.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eilong@broadcom.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).