From: Kiran Patil <kiran.patil@intel.com>
To: Roland Dreier <roland@kernel.org>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH] target: Make transport_lookup_cmd_lun() locking IRQ-safe
Date: Wed, 15 Jun 2011 13:53:56 -0700 [thread overview]
Message-ID: <4DF91BE4.5090105@intel.com> (raw)
In-Reply-To: <BANLkTimxM4OzQ6imbea0xqb3rmfBehfgEA@mail.gmail.com>
On 6/15/2011 12:41 PM, Roland Dreier wrote:
> On Wed, Jun 15, 2011 at 10:52 AM, Kiran Patil<kiran.patil@intel.com> wrote:
>> Likewise, we need to do same change in function "transport_get_lun_for_tmr",
>> specifically for tmr_lock. Please correct me if I am missing anything.
> Yes, that's right... in fact that is what we were discussing now, isn't it?
> Or is there something different I'm missing?
>
> (BTW transport_get_lun_for_tmr is renamed to transport_lookup_tmr_lun
> in the latest tree)
>
> - R.
Cool. Then we are referring to same function. Looks like I am using old
tree which has function name "transport_get_lun_for_tmr"
Thanks,
-- Kiran P,
next prev parent reply other threads:[~2011-06-15 20:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 3:44 [PATCH] target: Make transport_lookup_cmd_lun() locking IRQ-safe Roland Dreier
2011-06-14 8:12 ` Christoph Hellwig
2011-06-14 15:58 ` Roland Dreier
2011-06-16 12:15 ` Christoph Hellwig
2011-06-15 16:58 ` Nicholas A. Bellinger
2011-06-16 12:18 ` Christoph Hellwig
2011-06-15 17:06 ` Nicholas A. Bellinger
2011-06-15 17:22 ` Roland Dreier
2011-06-15 17:25 ` Nicholas A. Bellinger
2011-06-15 17:52 ` Kiran Patil
2011-06-15 19:41 ` Roland Dreier
2011-06-15 20:53 ` Kiran Patil [this message]
2011-06-15 18:53 ` Roland Dreier
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=4DF91BE4.5090105@intel.com \
--to=kiran.patil@intel.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=roland@kernel.org \
--cc=target-devel@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