From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Greg KH <greg@kroah.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Dave Jones <davej@codemonkey.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Summit support for 2.5 [0/4]
Date: Sun, 13 Oct 2002 20:09:23 -0700 [thread overview]
Message-ID: <1928331494.1034539762@[10.10.2.3]> (raw)
In-Reply-To: <20021014022515.GB1768@kroah.com>
>> PS. This distros want Summit to autodetect for their install kernels,
>> which is what the x86_summit switch is for.
>
> Why? Can't summit boot just fine on a i386 UP kernel? Then they can
> look at the chipset id and determine that they should install a
> summit-built kernel, right?
Probably could, but that's what they asked for. Maybe they don't mean
install kernel, but just running kernel in general. I presume they
don't want to maintain a seperate kernel just for Summit.
> Can this just be CONFIG_SUMMIT? I think most of these fixes need to be
> around for the ia64 version too :(
Nope, this is all under the i386 arch tree. ia64 can do what they
please, as far as I'm concerned.
> As we're going to end up with a mess of a ifdef nest over time with new
> archs added, how about something like this (completly untested):
Yeah, that was a quick hack by some idiot who doesn't speak much make ;-)
I'll steal Kai's thing from later in this thread.
> Other than that, looks like a good start to me (oh your email client is
> wrapping lines of the patch...)
Yeah, home email is borked for that, sorry. I'll do it properly when I
submit it.
M.
prev parent reply other threads:[~2002-10-14 3:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-13 20:41 Martin J. Bligh
2002-10-13 20:59 ` Greg KH
2002-10-13 21:06 ` Martin J. Bligh
2002-10-13 21:17 ` Greg KH
2002-10-13 21:31 ` Dave Jones
2002-10-13 22:15 ` Linus Torvalds
2002-10-14 2:02 ` Martin J. Bligh
2002-10-14 2:25 ` Greg KH
2002-10-14 2:49 ` Kai Germaschewski
2002-10-14 3:02 ` Greg KH
2002-10-14 5:46 ` Eric W. Biederman
2002-10-14 3:09 ` Martin J. Bligh [this message]
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='1928331494.1034539762@[10.10.2.3]' \
--to=mbligh@aracnet.com \
--cc=davej@codemonkey.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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®