From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/6] cnic: Fix ring setup/shutdown code
Date: Thu, 14 Jul 2011 08:46:33 -0700 (PDT) [thread overview]
Message-ID: <20110714.084633.1868435195489895600.davem@davemloft.net> (raw)
In-Reply-To: <1310613862-27497-3-git-send-email-mchan@broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Wed, 13 Jul 2011 20:24:19 -0700
> Latest bnx2x driver uses different CID for the iSCSI rings, so
> we need to pass it in the ring init data. The rx ring is also
> zeroed out to prevent stale DMA addresses from being used after
> shutdown.
>
> The same cp local variable redefined inside the else branch is
> also eliminated.
>
> Signed-off-by: Michael Chan <mchan@broadcom.com>
> Signed-off-by: Matt Carlson <mcarlson@broadcom.com>
Applied.
next prev parent reply other threads:[~2011-07-14 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 3:24 [PATCH net-next 1/6] cnic: Replace get_random_bytes() with random32() Michael Chan
2011-07-14 3:24 ` [PATCH net-next 2/6] cnic: Fix port_mode setting Michael Chan
2011-07-14 3:24 ` [PATCH net-next 3/6] cnic: Fix ring setup/shutdown code Michael Chan
2011-07-14 3:24 ` [PATCH net-next 4/6] cnic: Return proper error code if we fail to send netlink message Michael Chan
2011-07-14 3:24 ` [PATCH net-next 5/6] bnx2: Add MCP dump Michael Chan
2011-07-14 3:24 ` [PATCH net-next 6/6] bnx2: Read iSCSI config from shared memory during ->probe() Michael Chan
2011-07-14 15:46 ` David Miller
2011-07-14 15:46 ` [PATCH net-next 5/6] bnx2: Add MCP dump David Miller
2011-07-14 15:46 ` [PATCH net-next 4/6] cnic: Return proper error code if we fail to send netlink message David Miller
2011-07-14 15:46 ` David Miller [this message]
2011-07-14 15:46 ` [PATCH net-next 2/6] cnic: Fix port_mode setting David Miller
2011-07-14 15:46 ` [PATCH net-next 1/6] cnic: Replace get_random_bytes() with random32() David Miller
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=20110714.084633.1868435195489895600.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).