From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Uwe Bugla" <uwe.bugla@gmx.de>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux-dvb@linuxtv.org, domi.dumont@free.fr,
Jiri Slaby <jirislaby@gmail.com>,
bunk@stusta.de, linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@hpl.hp.com>,
venkatesh.pallipadi@intel.com
Subject: Re: 2.6.21-rc1-git2 is incompilable
Date: Thu, 1 Mar 2007 09:14:52 -0800 [thread overview]
Message-ID: <20070301091452.7f1bd700.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070301143407.29950@gmx.net>
On Thu, 01 Mar 2007 15:34:07 +0100 Uwe Bugla wrote:
> Hi folks,
> trying to compile kernel 2.6.21-rc1-git2 is impossible. The broken module where the compiler gives up is /arch/i386/kernel/io_apic.c.
>
> Regards
>
> Uwe
>
> P. S.: Wouldn't it be a good idea to test at least error-free compilation before stuff like this is being published?
1) 2.6.*-gitN kernels are automated snapshots of Linus's git kernel tree.
There is no coordination between Linus adding changesets to his kernel
tree and some script reading changes out of it. (I could read your
note as saying that there should be some coordination, I suppose.)
2) Linus doesn't build i386 non-SMP kernels AFAIK.
3) The small bug has been discussed & fixed (several times).
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-03-01 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 14:34 Uwe Bugla
2007-03-01 17:14 ` Randy Dunlap [this message]
2007-03-03 15:29 ` Uwe Bugla
2007-03-01 17:28 ` [linux-dvb] " Mws
2007-03-01 17:31 ` Marcel Siegert
2007-03-03 15:47 ` Uwe Bugla
2007-03-03 16:49 ` Marcel Siegert
2007-03-04 17:22 ` Thomas Gleixner
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=20070301091452.7f1bd700.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@stusta.de \
--cc=domi.dumont@free.fr \
--cc=eranian@hpl.hp.com \
--cc=jirislaby@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=uwe.bugla@gmx.de \
--cc=venkatesh.pallipadi@intel.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®