linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux-Scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] scsi: fix lockdep warning
Date: Sat, 20 Mar 2010 05:58:38 -0700	[thread overview]
Message-ID: <20100320125838.GA13626@suse.de> (raw)
In-Reply-To: <4BA47692.7040401@kernel.org>

On Sat, Mar 20, 2010 at 12:17:38AM -0700, Yinghai Lu wrote:
> 
> with qlogic and emulex card etc.

Is this still needed with 2.6.34-rc2?

And as was pointed out, this does not look correct as you are doing it
on static attributes.

thanks,

greg k-h

  parent reply	other threads:[~2010-03-20 13:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a4423d671003081547v5c955d58t248db945c06d2a7f@mail.gmail.com>
     [not found] ` <86802c441003081612r2f44efd6n9664b4b7c98a636a@mail.gmail.com>
     [not found]   ` <m1d3zel4b4.fsf@fess.ebiederm.org>
     [not found]     ` <4B95F37E.6060309@kernel.org>
     [not found]       ` <m14okqnczd.fsf@fess.ebiederm.org>
     [not found]         ` <4B99A6F0.4080203@kernel.org>
     [not found]           ` <4B9B0868.7080807@kernel.org>
2010-03-13  4:46             ` 2.6.34-rc1: ACPI: BUG: key f71f0168 not in .data! James Bottomley
2010-03-13  4:58               ` Eric W. Biederman
2010-03-13  5:13                 ` Matthew Wilcox
2010-03-20  7:17           ` [PATCH] scsi: fix lockdep warning Yinghai Lu
2010-03-20  7:57             ` Wolfram Sang
2010-03-20 12:58             ` Greg KH [this message]
2010-03-20 15:41             ` James Bottomley
2010-03-20 19:07               ` [PATCH] driver: fix lockdep with sysfs Yinghai Lu
2010-03-30 15:05             ` [PATCH] scsi: fix lockdep warning Ben Gamari
2010-03-30 17:08               ` Yinghai Lu
2010-03-30 20:33                 ` Ben Gamari
2010-03-31  1:55               ` Wolfram Sang

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=20100320125838.GA13626@suse.de \
    --to=gregkh@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=yinghai@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).