netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yanivr@broadcom.com
Cc: netdev@vger.kernel.org, eilong@broadcom.com
Subject: Re: [PATCH net-next 0/10] bnx2x: Few enhancements and styling fixes
Date: Mon, 31 Jan 2011 13:24:25 -0800 (PST)	[thread overview]
Message-ID: <20110131.132425.28815733.davem@davemloft.net> (raw)
In-Reply-To: <1296483683.17181.110.camel@lb-tlvb-dmitry>

From: "Yaniv Rosner" <yanivr@broadcom.com>
Date: Mon, 31 Jan 2011 16:21:23 +0200

> The following patch series describe some link enhancements and styling fixes in bnx2x driver.
> It should not cause conflicts when integrating the net-2.6.

How can it not cause conflicts, when there is a driver version update
in yesterday's net-2.6 patch set as well as this one.

> Please consider applying it to net-next.

I've applied this series to net-next-2.6, resolving the version conflict by
hand.

      reply	other threads:[~2011-01-31 21:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 14:21 [PATCH net-next 0/10] bnx2x: Few enhancements and styling fixes Yaniv Rosner
2011-01-31 21:24 ` 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=20110131.132425.28815733.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eilong@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=yanivr@broadcom.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).