lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100923191629.GB18736@kroah.com>
Date:	Thu, 23 Sep 2010 12:16:29 -0700
From:	Greg KH <greg@...ah.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Kay Sievers <kay.sievers@...y.org>, gregkh@...e.de,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -next] driver core: fix build for CONFIG_BLOCK=n

On Thu, Sep 23, 2010 at 11:15:41AM -0700, Randy Dunlap wrote:
> On Tue, 21 Sep 2010 15:31:15 -0700 Greg KH wrote:
> 
> > On Mon, Sep 20, 2010 at 09:20:34AM -0700, Randy Dunlap wrote:
> > > From: Randy Dunlap <randy.dunlap@...cle.com>
> > > 
> > > Fix build when CONFIG_BLOCK is not enabled (since SEP-06).
> > > Fixes these build errors:
> > > 
> > > drivers/base/core.c: In function 'get_device_parent':
> > > drivers/base/core.c:622: error: 'block_class' undeclared (first use in this function)
> > > drivers/base/core.c: In function 'device_add_class_symlinks':
> > > drivers/base/core.c:712: error: 'block_class' undeclared (first use in this function)
> > > drivers/base/core.c: In function 'device_remove_class_symlinks':
> > > drivers/base/core.c:742: error: 'block_class' undeclared (first use in this function)
> > > 
> > > Signed-off-by: Randy Dunlap <randy.dunlap@...cle.com>
> > 
> > This should no longer be needed with the next linux-next tree as the
> > logic in this area has changed thanks to Andi's patch.
> 
> {sorry about resend, email problems}
> 
> 
> Still seeing this build error. (linux-next 2010-0923)
> Will you be merging some patch soon?

Not unless someone provides it.  I know of no valid user of the kernel
that does not enable CONFIG_BLOCK, so I really doubt this will ever hit
anyone in "real life" so it's _way_ down the list of things I have to do
at the moment, sorry.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ