From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Rasesh Mody <rmody@brocade.com>
Cc: netdev@vger.kernel.org, adapter_linux_open_src_team@brocade.com
Subject: Re: Subject: [PATCH 1/6] bna: Brocade 10Gb Ethernet device driver
Date: Mon, 22 Feb 2010 13:40:05 +0100 [thread overview]
Message-ID: <20100222124004.GD2520@dhcp-lab-161.englab.brq.redhat.com> (raw)
In-Reply-To: <201002192152.o1JLqc8G031956@blc-10-1.brocade.com>
On Fri, Feb 19, 2010 at 01:52:38PM -0800, Rasesh Mody wrote:
> From: Rasesh Mody <rmody@brocade.com>
>
> This is patch 1/6 which contains linux driver source for
> Brocade's BR1010/BR1020 10Gb CEE capable ethernet adapter.
> Source is based against net-next-2.6.
>
> We wish this patch to be considered for inclusion in net-next-2.6
>
> Signed-off-by: Rasesh Mody <rmody@brocade.com>
> ---
> bnad.c | 3481 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> bnad.h | 341 ++++++
> 2 files changed, 3822 insertions(+)
[snip]
> void bnad_ioc_timeout(unsigned long ioc_arg)
> +{
> + struct bnad *bnad = (struct bnad *)(((struct bfa_ioc*)ioc_arg)->bfa);
> + spin_lock_irq(&bnad->priv_lock);
> + spin_unlock_irq(&bnad->priv_lock);
Quite strange spin lock usage :)
> +u32
> +bnad_get_msglevel(struct net_device *netdev)
> +{
> + return bnad_log_level;
> +}
> +
> +void
> +bnad_set_msglevel(struct net_device *netdev, u32 msglevel)
> +{
> + struct bnad *bnad = netdev_priv(netdev);
> + mutex_lock(&bnad->conf_mutex);
> + bnad_log_level = msglevel;
> + mutex_unlock(&bnad->conf_mutex);
> +}
bnad_log_level is not used anywhere.
next prev parent reply other threads:[~2010-02-22 12:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 21:52 Subject: [PATCH 1/6] bna: Brocade 10Gb Ethernet device driver Rasesh Mody
2010-02-22 12:40 ` Stanislaw Gruszka [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-12 14:00 Rasesh Mody
2010-02-10 6:29 Rasesh Mody
2010-02-10 17:08 ` Stephen Hemminger
2010-02-10 17:09 ` Stephen Hemminger
2010-02-10 17:10 ` Stephen Hemminger
2010-02-10 17:15 ` Stephen Hemminger
2009-12-19 1:28 Debashis Dutt
2009-12-19 7:14 ` Joe Perches
2009-11-26 9:28 Debashis Dutt
2009-11-24 3:51 Rasesh Mody
2009-11-17 8:30 Rasesh Mody
2009-11-17 8:59 ` David Miller
2009-11-13 3:46 Rasesh Mody
2009-11-01 5:03 Rasesh Mody
2009-11-01 5:23 ` Joe Perches
2009-11-01 19:25 ` Stephen Hemminger
2009-11-03 3:14 ` Debashis Dutt
2009-11-03 3:34 ` Greg KH
2009-11-03 18:24 ` Rasesh Mody
2009-11-04 0:31 ` Joe Perches
2009-11-01 8:02 ` Eric Dumazet
2009-11-03 7:54 ` Debashis Dutt
2009-11-01 19:19 ` Stephen Hemminger
2009-11-03 3:05 ` Debashis Dutt
2009-10-16 18:24 Rasesh Mody
2009-10-16 20:20 ` Ben Hutchings
2009-10-16 23:19 ` Rasesh Mody
2009-10-20 0:54 ` Herbert Xu
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=20100222124004.GD2520@dhcp-lab-161.englab.brq.redhat.com \
--to=sgruszka@redhat.com \
--cc=adapter_linux_open_src_team@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).