From: Andrew Morton <akpm@osdl.org>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: jdike@addtoit.com, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/22] UML - Include the linker script rather than symlink it
Date: Mon, 2 May 2005 18:28:51 -0700 [thread overview]
Message-ID: <20050502182851.27f22470.akpm@osdl.org> (raw)
In-Reply-To: <20050503011744.GC18977@parcelfarce.linux.theplanet.co.uk>
Al Viro <viro@parcelfarce.linux.theplanet.co.uk> wrote:
>
> On Mon, May 02, 2005 at 05:44:05PM -0700, Andrew Morton wrote:
> >
> > There's a bit of a tangle going on in arch/um/kernel/Makefile, but it's
> > fairly simple stuff.
> >
> > I put a rolled-up patch against 2.6.12-rc3 at
> > http://www.zip.com.au/~akpm/linux/patches/stuff/x.bz2 if someone wants to
> > check it all.
>
> Broken, due to missing mk_sc patch (it should go before mk_thread one;
OK. I ended up with an odd-looking arch/um/sys-x86_64/util/Makefile:
# Copyright 2003 - 2004 Pathscale, Inc
# Released under the GPL
hostprogs-y := mk_sc mk_thread
always := $(hostprogs-y)
HOSTCFLAGS_mk_thread.o := -I$(objtree)/arch/um
Is mk_sc still supposed to be in there?
> how the hell did the latter manage to apply at all?)
I just "fixed" things. I do it all the time.
> > Is this all considered post-2.6.12 material?
>
> Once all patches are in there - up to Jeff ;-) Seriously, kbuild patchkit
> is decently tested and has obviously no impact on other architectures. So
> that one is up to maintainer of architecture in question...
OK..
next prev parent reply other threads:[~2005-05-03 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 21:12 Jeff Dike
2005-05-03 0:06 ` Andrew Morton
2005-05-03 0:25 ` Al Viro
2005-05-03 0:44 ` Andrew Morton
2005-05-03 1:17 ` Al Viro
2005-05-03 1:28 ` Andrew Morton [this message]
2005-05-03 1:45 ` Al Viro
2005-05-03 2:02 ` Andrew Morton
2005-05-03 3:03 ` Jeff Dike
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=20050502182851.27f22470.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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®