From: Keith Owens <kaos@ocs.com.au>
To: Michael Rothwell <rothwell@holly-springs.nc.us>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org,
Eyal Lebedinsky <eyal@eyal.emu.id.au>
Subject: Re: Linux 2.2.18 almost...
Date: Sun, 10 Dec 2000 11:17:43 +1100 [thread overview]
Message-ID: <15713.976407463@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 09 Dec 2000 18:32:56 CDT." <3A32C128.1ED29FA2@holly-springs.nc.us>
On Sat, 09 Dec 2000 18:32:56 -0500,
Michael Rothwell <rothwell@holly-springs.nc.us> wrote:
>Alan Cox wrote:
>> The patch I intend to be 2.2.18 is out as 2.2.18pre26 in the usual place.
>> I'll move it over tomorrow if nobody reports any horrors, missing files etc
>
>Fresh 2.2.17, "patch -p1 < /pre-patch-2.2.18-26"
>
>can't find file to patch at input line 38909
>Perhaps you used the wrong -p or --strip option?
>The text leading up to this was:
>--------------------------
>|diff -u --new-file --recursive --exclude-from /usr/src/exclude
>v2.2.17/arch/i386/vmlinux.lds linux/arch/i386/vmlinux.lds
>|--- v2.2.17/arch/i386/vmlinux.lds Wed May 3 21:22:13 2000
>|+++ linux/arch/i386/vmlinux.lds Sat Dec 9 21:23:21 2000
Ignore that bit of the patch. arch/i386/vmlinux.lds is generated from
arch/i386/vmlinux.lds.S and the latter is correctly patched. The patch
for arch/i386/vmlinux.lds should not have been generated.
<rant size="small">
There are a lot of unnecessary inconsistencies between architectures.
Some archs generate vmlinux.lds from vmlinux.lds.S, some from
vmlinux.lds.in, some do not generate vmlinux.lds, it is shipped in the
tarball. The inconsistencies make it difficult to distinguish between
files that are generated (not shipped, ignore for patching) and master
files (shipped in tar ball, check for patches).
There is a similar problem with oops text. Each architecture needs an
oops report but each one prints it differently.
I implore architecture maintainers to adopt a common approach to
generated files, oops reports etc. Remember that each arch needs to be
part of the common tar ball and has to operate with a single set of
make and other user space tools.
</rant>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-10 0:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 23:00 Linux 2.2.18 almost Alan Cox
2000-12-09 23:12 ` Tom Rini
2000-12-09 23:36 ` Eyal Lebedinsky
2000-12-09 23:32 ` Michael Rothwell
2000-12-10 0:17 ` Keith Owens [this message]
2000-12-10 0:23 ` Andre Hedrick
2000-12-10 1:11 ` Alan Cox
2000-12-10 8:29 ` Tigran Aivazian
2000-12-10 8:34 ` Tigran Aivazian
2000-12-10 18:20 ` Alan Cox
2000-12-10 16:34 ` Vasil Kolev
2000-12-11 9:26 ` Eddy
2000-12-11 13:03 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2000-12-11 10:44 Luca Montecchiani
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=15713.976407463@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eyal@eyal.emu.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rothwell@holly-springs.nc.us \
/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