From: "Bhanu Prakash Gollapudi" <bprakash@broadcom.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi@vger.kernel.org, Mike Christie <michaelc@cs.wisc.edu>,
Bhanu Prakash Gollapudi <bprakash@broadcom.com>
Subject: Re: [v2 PATCH 0/4] bnx2fc version 1.0.11
Date: Mon, 21 May 2012 11:35:02 -0700 [thread overview]
Message-ID: <4FBA8AD6.70107@broadcom.com> (raw)
In-Reply-To: <1337623588.16400.5.camel@dabdike.int.hansenpartnership.com>
On 5/21/2012 11:06 AM, James Bottomley wrote:
> On Mon, 2012-05-21 at 09:18 -0700, Bhanu Prakash Gollapudi wrote:
>> On 4/24/2012 3:26 PM, Bhanu Prakash Gollapudi wrote:
>>
>> James, can you please include this patch set in the next round of 3.4+
>> merge window?
>
> I was waiting for you to respond to Mike Christie's comment about using
> list_for_each_entry_safe() or list_entry().
James, I responded to Mike Christie's comment. Here is the link for the
thread - http://marc.info/?l=linux-scsi&m=133643754200805&w=2.
thanks,
Bhanu
>
> James
>
>
>
next prev parent reply other threads:[~2012-05-21 18:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 22:26 [v2 PATCH 0/4] bnx2fc version 1.0.11 Bhanu Prakash Gollapudi
2012-04-24 22:26 ` [v2 PATCH 1/4] bnx2fc: Allow FLOGI to be retried when receiving bad responses Bhanu Prakash Gollapudi
2012-04-24 22:26 ` [v2 PATCH 2/4] bnx2fc: Decrememnt io ref count when abort times out Bhanu Prakash Gollapudi
2012-04-24 22:26 ` [v2 PATCH 3/4] bnx2fc: cleanup task management IO when it " Bhanu Prakash Gollapudi
2012-05-04 8:49 ` Mike Christie
2012-04-24 22:26 ` [v2 PATCH 4/4] Bumped version to 1.0.11 Bhanu Prakash Gollapudi
2012-05-21 16:18 ` [v2 PATCH 0/4] bnx2fc version 1.0.11 Bhanu Prakash Gollapudi
2012-05-21 18:06 ` James Bottomley
2012-05-21 18:35 ` Bhanu Prakash Gollapudi [this message]
2012-05-22 8:45 ` James Bottomley
2012-05-22 17:06 ` Bhanu Prakash Gollapudi
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=4FBA8AD6.70107@broadcom.com \
--to=bprakash@broadcom.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.