From: David Miller <davem@davemloft.net>
To: rmody@brocade.com
Cc: netdev@vger.kernel.org, amathur@brocade.com, ddutt@brocade.com,
huangj@brocade.com
Subject: Re: [PATCH net-next-2.6] bna: Fixed build break for allyesconfig
Date: Wed, 25 Aug 2010 23:45:19 -0700 (PDT) [thread overview]
Message-ID: <20100825.234519.112609091.davem@davemloft.net> (raw)
In-Reply-To: <201008260557.o7Q5v8AU028127@blc-10-10.brocade.com>
From: Rasesh Mody <rmody@brocade.com>
Date: Wed, 25 Aug 2010 22:57:08 -0700
> From: Rasesh Mody <rmody@brocade.com>
>
> This is the patch to fix the build break caused by multiple
> definitions of symbols between Brocade's FC/FCOE driver(BFA)
> and 10G Networking Driver(BNA).
>
> Changes are:
>
> 1. locally used functions are made static
>
> 2. unused functions are removed
>
> 3. using unique namespaces for the function names that must be
> globally visible
>
> Signed-off-by: Debashis Dutt <ddutt@brocade.com>
> Signed-off-by: Rasesh Mody <rmody@brocade.com>
Applied, thanks.
prev parent reply other threads:[~2010-08-26 6:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 5:57 [PATCH net-next-2.6] bna: Fixed build break for allyesconfig Rasesh Mody
2010-08-26 6: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=20100825.234519.112609091.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=amathur@brocade.com \
--cc=ddutt@brocade.com \
--cc=huangj@brocade.com \
--cc=netdev@vger.kernel.org \
--cc=rmody@brocade.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).