From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH -next 1/6] bnx2: Check BNX2_FLAG_USING_MSIX flag when setting up MSIX.
Date: Tue, 16 Feb 2010 15:20:05 -0800 (PST) [thread overview]
Message-ID: <20100216.152005.98313418.davem@davemloft.net> (raw)
In-Reply-To: <1266298932-28129-1-git-send-email-mchan@broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Mon, 15 Feb 2010 21:42:07 -0800
> Checking the flag is more correct than checking bp->irq_nvecs. By
> accident it is not a problem because we always have more than 1
> vectors when using MSIX mode.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
> Signed-off-by: Benjamin Li <benli@broadcom.com>
Applied.
prev parent reply other threads:[~2010-02-16 23:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 5:42 [PATCH -next 1/6] bnx2: Check BNX2_FLAG_USING_MSIX flag when setting up MSIX Michael Chan
2010-02-16 5:42 ` [PATCH -next 2/6] bnx2: Need to call cnic_setup_cnic_irq_info() after MTU change Michael Chan
2010-02-16 5:42 ` [PATCH -next 3/6] bnx2: Adjust flow control water marks Michael Chan
2010-02-16 5:42 ` [PATCH -next 4/6] bnx2: Allow user-specified multiple advertisement speed values Michael Chan
2010-02-16 5:42 ` [PATCH -next 5/6] bnx2: Fix bug when saving statistics Michael Chan
2010-02-16 23:20 ` David Miller
[not found] ` <1266298932-28129-6-git-send-email-mchan@broadcom.com>
2010-02-16 23:20 ` [PATCH -next 6/6] bnx2: Update firmwares and update version to 2.0.8 David Miller
2010-02-16 23:20 ` [PATCH -next 4/6] bnx2: Allow user-specified multiple advertisement speed values David Miller
2010-02-16 23:20 ` [PATCH -next 3/6] bnx2: Adjust flow control water marks David Miller
2010-02-16 23:20 ` [PATCH -next 2/6] bnx2: Need to call cnic_setup_cnic_irq_info() after MTU change David Miller
2010-02-16 23:20 ` 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=20100216.152005.98313418.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mchan@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).