From: Greg KH <gregkh@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
Randy Dunlap <rdunlap@xenotime.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: compile error in current git
Date: Fri, 25 Jan 2008 14:17:31 -0800 [thread overview]
Message-ID: <20080125221731.GB15172@suse.de> (raw)
In-Reply-To: <479A4867.9040302@goop.org>
On Fri, Jan 25, 2008 at 12:36:55PM -0800, Jeremy Fitzhardinge wrote:
> When compiling current git with CONFIG_BLOCK disabled, I'm seeing this
> compile error:
>
> CC drivers/base/core.o
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c: In function
> ???device_add_class_symlinks???:
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c:655: error:
> ???part_type??? undeclared (first use in this function)
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c:655: error: (Each
> undeclared identifier is reported only once
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c:655: error: for each
> function it appears in.)
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c: In function
> ???device_remove_class_symlinks???:
> /home/jeremy/hg/xen/paravirt/linux/drivers/base/core.c:728: error:
> ???part_type??? undeclared (first use in this function)
> make[4]: *** [drivers/base/core.o] Error 1
Hm, I thought we fixed the CONFIG_BLOCK disabled issues with Randy's
older patch. Randy, wasn't this already addressed somehow?
Jeremy, do you have a .config I can use to try to duplicate and fix
this?
thanks,
greg k-h
next prev parent reply other threads:[~2008-01-25 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 20:36 compile error in current git Jeremy Fitzhardinge
2008-01-25 22:17 ` Greg KH [this message]
2008-01-25 23:00 ` Randy Dunlap
2008-01-25 23:11 ` Greg KH
2008-01-25 23:24 ` Jeremy Fitzhardinge
2008-01-26 9:14 ` [Patch] drivers/base/core.c: fix a compile error WANG Cong
2008-01-27 19:40 ` Greg KH
2008-01-28 5:19 ` WANG Cong
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=20080125221731.GB15172@suse.de \
--to=gregkh@suse.de \
--cc=jeremy@goop.org \
--cc=linux-kernel@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.