From: Arjan van de Ven <arjan@fenrus.demon.nl>
To: Matthew Wilcox <matthew@wil.cx>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Roman Zippel <zippel@linux-m68k.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
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: Wed, 01 Nov 2006 17:18:40 +0100 [thread overview]
Message-ID: <1162397920.23744.28.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20061101153623.GF11399@parisc-linux.org>
On Wed, 2006-11-01 at 08:36 -0700, Matthew Wilcox wrote:
> On Thu, Nov 02, 2006 at 12:26:54AM +0900, James Bottomley wrote:
> > On Wed, 2006-11-01 at 01:00 +0100, Roman Zippel wrote:
> > > Please don't select NET, it's way too broad.
> >
> > Then you'll make select implied dependencies work in Kbuild so we don't
> > need to do anything at all about this?
>
> This is iSCSI ... how can it possibly be useful without NET? Why
> doesn't CONFIG_ISCSI depend on NET, making this whole problem moot (for
> now).
I doubt ANYONE runs without NET; just WAY too much stuff breaks (not
even unix sockets work!)
next prev parent reply other threads:[~2006-11-01 16:19 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
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 [this message]
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=1162397920.23744.28.camel@laptopd505.fenrus.org \
--to=arjan@fenrus.demon.nl \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=randy.dunlap@oracle.com \
--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