From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Randy Dunlap <RANDY.DUNLAP@ORACLE.COM>
Cc: linux-kernel@vger.kernel.org, philipp.zabel@gmail.com
Subject: Re: pasic3 allmod/yesconfig build error
Date: Tue, 22 Apr 2008 20:49:33 +0100 [thread overview]
Message-ID: <20080422194933.GB9911@flint.arm.linux.org.uk> (raw)
In-Reply-To: <28221442.1208881240429.JavaMail.oracle@acsmt302.oracle.com>
On Tue, Apr 22, 2008 at 11:20:40AM -0500, Randy Dunlap wrote:
> allmodconfig and allyesconfig on $ARCH try to build the htc-pasic3 driver,
> but it fails due to wanting <asm/arch/pxa-regs.h>.
>
> Should the Kconfig file be modified to build this driver only for $ARCH=arm ?
Known problem. You're about the 4th person in the last 24 hours to
report this.
It's been known about since Sunday. Unfortunately, Linus not responding
to emails until midnight (my time) on Monday meant that I've not been able
to do anything about it, despite having a fix (along with others) already
merged but not properly queued up (because I didn't know what Linus was
going to do.)
So... I'm not going to be able to properly sort my tree until Thursday.
Please ignore it until Friday. Thanks.
(Please note that these reports are stressing me because I have the fix,
I've known about it for ages, but because of factors out of my control -
and community policy, in so far as "you do not change the tree you've asked
to be pulled from" I'd have been unable to resolve it and all the other
stupid breakage in that pull before anyone saw it. I suppose what I
should've done was deleted the tree of kernel.org so Linus _couldn't_
pull it.)
next prev parent reply other threads:[~2008-04-22 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 16:20 Randy Dunlap
2008-04-22 19:49 ` Russell King - ARM Linux [this message]
2008-04-22 20:03 ` Harvey Harrison
2008-04-22 20:14 ` Russell King - ARM Linux
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=20080422194933.GB9911@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=RANDY.DUNLAP@ORACLE.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.zabel@gmail.com \
/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
all inboxes | Powered by JetHome®