public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
	Toralf F_rster <toralf.foerster@gmx.de>,
	scsi <linux-scsi@vger.kernel.org>, akpm <akpm@osdl.org>
Subject: Re: [PATCH] SCSI: ISCSI build failure
Date: Tue, 31 Oct 2006 12:49:25 -0800	[thread overview]
Message-ID: <4547B6D5.1050208@oracle.com> (raw)
In-Reply-To: <1162327892.13859.67.camel@mulgrave.il.steeleye.com>

James Bottomley wrote:
> On Mon, 2006-10-30 at 08:32 -0800, Randy Dunlap wrote:
>>> I guess, that needs a dependency on NET.
> 
> Actually, my first thought is that the select should give us an implied
> NET dependency, since the thing we've selected depends on NET.

Agreed.  :(

> However, if that's impossible in the Kbuild system, we should eliminate
> the dependency duplication and simply make SCSI_ISCSI_ATTRS depend on
> SCSI but select NET.  That will avoid this problem for any other
> attribute users in future.

I'd prefer to avoid the use of 'select' if at all possible.

-- 
~Randy

  reply	other threads:[~2006-10-31 20:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 18:45 Fwd: linux-2.6.19-rc3-g2da6dc28 build #105 failed Toralf Förster
2006-10-30  3:03 ` Randy Dunlap
2006-10-30 11:07   ` Roman Zippel
2006-10-30 16:32     ` [PATCH] SCSI: ISCSI build failure Randy Dunlap
2006-10-31 20:51       ` James Bottomley
2006-10-31 20:49         ` Randy Dunlap [this message]
2006-10-31 21:03           ` James Bottomley
2006-10-31 21:02             ` Randy Dunlap
2006-10-31 21:12               ` James Bottomley
2006-10-31 21:13                 ` Randy Dunlap
2006-11-01  0:00         ` Roman Zippel
2006-11-01 15:26           ` James Bottomley
2006-11-01 15:36             ` Matthew Wilcox
2006-11-01 16:03               ` Randy Dunlap
2006-11-01 16:18               ` Arjan van de Ven
2006-11-01 21:57               ` James Bottomley

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=4547B6D5.1050208@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    --cc=zippel@linux-m68k.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