public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: roopa <roopa@cumulusnetworks•com>
To: "Rosen, Rami" <rami.rosen@intel•com>
Cc: "jiri@resnulli•us" <jiri@resnulli•us>,
	"sfeldma@gmail•com" <sfeldma@gmail•com>,
	"jhs@mojatatu•com" <jhs@mojatatu•com>,
	"bcrl@kvack•org" <bcrl@kvack•org>,
	"tgraf@suug•ch" <tgraf@suug•ch>,
	"john.fastabend@gmail•com" <john.fastabend@gmail•com>,
	"stephen@networkplumber•org" <stephen@networkplumber•org>,
	"vyasevic@redhat•com" <vyasevic@redhat•com>,
	"Arad, Ronen" <ronen.arad@intel•com>,
	"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
	"davem@davemloft•net" <davem@davemloft•net>,
	"shm@cumulusnetworks•com" <shm@cumulusnetworks•com>,
	"gospo@cumulusnetworks•com" <gospo@cumulusnetworks•com>
Subject: Re: [PATCH net-next v3 3/5] bridge: offload bridge port attributes to switch asic if feature flag set
Date: Fri, 23 Jan 2015 07:59:55 -0800	[thread overview]
Message-ID: <54C26FFB.1050908@cumulusnetworks.com> (raw)
In-Reply-To: <9B0331B6EBBD0E4684FBFAEDA55776F9189065DD@HASMSX110.ger.corp.intel.com>

On 1/23/15, 4:53 AM, Rosen, Rami wrote:
> Hi,
> There is another Linux Ethernet driver which defines the ndo_bridge_setlink() callback, which is not included in the patch. It is the
> Emulex ServerEngines' 10Gbps NIC (BladeEngine) (drivers/net/ethernet/emulex/benet).
> So once the CONFIG_BE2NET kernel config item is set, running make will emit a compile warning.
>
>
Thanks for catching this and your other comment. will fix them in the 
next version.

      reply	other threads:[~2015-01-23 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23  4:33 [PATCH net-next v3 3/5] bridge: offload bridge port attributes to switch asic if feature flag set roopa
2015-01-23 12:53 ` Rosen, Rami
2015-01-23 15:59   ` roopa [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=54C26FFB.1050908@cumulusnetworks.com \
    --to=roopa@cumulusnetworks$(echo .)com \
    --cc=bcrl@kvack$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=gospo@cumulusnetworks$(echo .)com \
    --cc=jhs@mojatatu$(echo .)com \
    --cc=jiri@resnulli$(echo .)us \
    --cc=john.fastabend@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rami.rosen@intel$(echo .)com \
    --cc=ronen.arad@intel$(echo .)com \
    --cc=sfeldma@gmail$(echo .)com \
    --cc=shm@cumulusnetworks$(echo .)com \
    --cc=stephen@networkplumber$(echo .)org \
    --cc=tgraf@suug$(echo .)ch \
    --cc=vyasevic@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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