linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>
Subject: Re: linux-next: Tree for January 19 (DST)
Date: Mon, 19 Jan 2009 21:30:47 +0300	[thread overview]
Message-ID: <20090119183046.GA28947@ioremap.net> (raw)
In-Reply-To: <4974C288.7030301@oracle.com>

Hi Randy.

On Mon, Jan 19, 2009 at 10:12:24AM -0800, Randy Dunlap (randy.dunlap@oracle.com) wrote:
> > There will be no build results for today's linux-next as our build server
> > has failed.
> > 
> > Changes since 20090116:
> 
> 
> DST build fails when CONFIG_BLOCK=n:

DST should depend on block and block device, in the original patch its
kconfig entry was in the BLK_DEV menu, so this dependency was satisfied
automatically. Should attached patch be pushed into drivers/staging?

--- ./drivers/staging/dst/Kconfig~	2009-01-14 02:10:02.000000000 +0300
+++ ./drivers/staging/dst/Kconfig	2009-01-19 21:31:19.000000000 +0300
@@ -1,6 +1,6 @@
 config DST
 	tristate "Distributed storage"
-	depends on NET && CRYPTO && SYSFS
+	depends on NET && CRYPTO && SYSFS && BLK_DEV
 	select CONNECTOR
 	---help---
 	DST is a network block device storage, which can be used to organize

-- 
	Evgeniy Polyakov

  reply	other threads:[~2009-01-19 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19  6:27 linux-next: Tree for January 19 Stephen Rothwell
2009-01-19 18:12 ` linux-next: Tree for January 19 (DST) Randy Dunlap
2009-01-19 18:30   ` Evgeniy Polyakov [this message]
2009-01-19 18:47     ` Randy Dunlap
2009-01-19 18:57       ` Greg KH
2009-01-19 18:17 ` linux-next: Tree for January 19 (x86_32 sub-arch) 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=20090119183046.GA28947@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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).