From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Philipp Zabel <philipp.zabel@gmail.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: Linus' tree build breakage
Date: Tue, 22 Apr 2008 08:36:22 +0100 [thread overview]
Message-ID: <20080422073622.GB22955@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080422103111.e1d38371.sfr@canb.auug.org.au>
On Tue, Apr 22, 2008 at 10:31:11AM +1000, Stephen Rothwell wrote:
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/mfd/htc-pasic3.c:22:31: error: asm/arch/pxa-regs.h: No such file or directory
>
> I have reverted commit 5dc3339aa5ba29593ea57814049ddca8c12831c8 ("[ARM]
> 4964/1: htc-pasic3: MFD driver for PASIC3 LED control + DS1WM chip") as
> the easiest thing.
That's known from the -mm tree since last week. It's not the only thing
that's wrong.
I had asked Linus on Monday morning _not_ to pull my tree because there's
various problems with it. Unfortunately, though Linus didn't see that
before he pulled it and I now have a rapidly growing set of fixes.
It will be towards the end of this week before I'll be able to finish
resolving the problems.
> Russell, this is why I would have liked you to participate in the
> linux-next tree ...
linux-next will not give me anything which -mm isn't giving me. As I
said in the discussion, linux-next value is _very_ small for me.
Sorry but true.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-04-22 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 0:31 Stephen Rothwell
2008-04-22 7:36 ` Russell King [this message]
2008-04-22 7:43 ` David Miller
2008-04-22 13:58 ` Andrew Morton
2008-04-22 15:04 ` Stephen Rothwell
2008-04-22 22:30 ` Greg KH
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=20080422073622.GB22955@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=philipp.zabel@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®