From: Stephen Rothwell <sfr@canb.auug.org.au>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-next@vger.kernel.org, akpm <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH -next] scsi: RAID_ATTRS depends on SCSI
Date: Wed, 3 Mar 2010 17:17:20 +1100 [thread overview]
Message-ID: <20100303171720.95a558b6.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1267594617.4383.24.camel@mulgrave.site>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
Hi James,
On Wed, 03 Mar 2010 11:06:56 +0530 James Bottomley <James.Bottomley@suse.de> wrote:
>
> This will fix the error, but it's not quite the right thing to do. the
> RAID class should be independent of SCSI, but it wants to do a SCSI
> check if SCSI is compiled in the matching routines. This gives us a
> nasty dependency, the condition being that the raid class must be m if
> SCSI is m.
>
> I think this patch does the right thing. Can someone test it on the
> config checker? Or I can just put it in linux-next and have Stephen's
> builds do it.
My tree for today has Randy's fix in it. Also, you should really test
against Linus' tree as that is where the problem currently lies.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-03 6:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 6:47 linux-next: Tree for February 19 Stephen Rothwell
2010-02-19 17:21 ` linux-next: Tree for February 19 (scsi/mpt2sas/raid_class) Randy Dunlap
2010-02-22 3:46 ` [PATCH -next] scsi: RAID_ATTRS depends on SCSI Randy Dunlap
2010-03-02 11:26 ` [origin tree build failure] " Ingo Molnar
2010-03-02 23:30 ` Stephen Rothwell
2010-03-03 5:36 ` James Bottomley
2010-03-03 6:17 ` Stephen Rothwell [this message]
2010-03-03 16:56 ` Randy Dunlap
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=20100303171720.95a558b6.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=James.Bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.