From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: Andrew Morton <akpm@osdl.org>
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: Tue, 3 May 2005 02:45:43 +0100 [thread overview]
Message-ID: <20050503014543.GD18977@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050502182851.27f22470.akpm@osdl.org>
On Mon, May 02, 2005 at 06:28:51PM -0700, Andrew Morton wrote:
> # 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?
Yes, along with hostflags for it.
> > how the hell did the latter manage to apply at all?)
>
> I just "fixed" things. I do it all the time.
Erm... "Gives rejects" => "ought to investigate" => "bugger it, let
submitter figure it out and resubmit" would be an obvious progression...
OK. Please, pick the following patches:
UM0-uml-ldscript-RC12-rc3
UM1-uml-os-RC12-rc3
UM2-uml-user-constants-RC12-rc3
UM3-uml-ptregs-RC12-rc3
UM4-uml-sc-RC12-rc3
UM5-uml-kernel-offsets-RC12-rc3
UM6-uml-thread-RC12-rc3
UM7-uml-util-RC12-rc3
UM8-uml-clean-RC12-rc3
UM10-uml-O-RC12-rc3
in ftp.linux.org.uk/pub/people/viro. In the order above. That's where
the beginning of Jeff's series had come from (his 1--9 and 4.5).
(In case if you wonder about UM9, that one already has an equivalent in
-mm).
next prev parent reply other threads:[~2005-05-03 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 21:12 [PATCH 1/22] UML - Include the linker script rather than symlink it 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
2005-05-03 1:45 ` Al Viro [this message]
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=20050503014543.GD18977@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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