From: David Miller <davem@davemloft.net>
To: eilong@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [net-next 0/8] bnx2x: Device Control Channel bug fixes
Date: Wed, 14 Oct 2009 16:57:04 -0700 (PDT) [thread overview]
Message-ID: <20091014.165704.59488176.davem@davemloft.net> (raw)
In-Reply-To: <20091014.150922.64618889.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Wed, 14 Oct 2009 15:09:22 -0700 (PDT)
> Applied to net-next-2.6, which is where this likely belongs.
Eilon I somehow screwed up this patch set, and largely that is
because the firmware patch was too large for the list and therefore
it didn't end up in patchwork.
I tried to force in the private copy you sent me into the bundle
I applied, but I screwed that up somehow.
Could you please privately send me this whole patch set again so I can
try to apply it properly?
Thanks!
next prev parent reply other threads:[~2009-10-14 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 15:07 [net-next 0/8] bnx2x: Device Control Channel bug fixes Eilon Greenstein
2009-10-14 22:09 ` David Miller
2009-10-14 23:57 ` David Miller [this message]
2009-10-15 6:47 ` Eilon Greenstein
2009-10-15 7:23 ` 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=20091014.165704.59488176.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).