From: David Greaves <david@dgreaves.com>
To: Sam Ravnborg <sam@ravnborg.org>,
"Randy.Dunlap" <rddunlap@osdl.org>,
greg@kroah.com
Cc: Greg Norris <haphazard@kc.rr.com>,
linux-kernel@vger.kernel.org, akpm <akpm@osdl.org>
Subject: [BUG] Re: [PATCH] scripts/patch-kernel: use EXTRAVERSION
Date: Tue, 15 Mar 2005 16:15:54 +0000 [thread overview]
Message-ID: <42370A3A.6020206@dgreaves.com> (raw)
In-Reply-To: <20040822204002.GB8639@mars.ravnborg.org>
Old thread (!) but this is the last time I could find patch-kernel updated.
Sam Ravnborg wrote:
>On Wed, Aug 18, 2004 at 01:57:51PM -0700, Randy.Dunlap wrote:
>
>
>>Update 'scripts/patch-kernel' to support EXTRAVERSION.
>>
>>
>
>I saw no complains, so applied.
>
>
FYI
$ ./scripts/patch-kernel . /everything/Downloads/Linux/SOURCES/kernel/
Current kernel version is 2.6.10 (Woozy Numbat)
Applying patch-2.6.11 (gzip)... done.
Applying patch-2.6.11.1 (gzip)... done.
Applying patch-2.6.11.2 (gzip)... done.
Applying patch-2.6.11.3 (gzip)... 1 out of 1 hunk FAILED -- saving
rejects to file Makefile.rej
Reversed (or previously applied) patch detected! Skipping patch.
3 out of 3 hunks ignored -- saving rejects to file
drivers/input/serio/i8042-x86ia64io.h.rej
Reversed (or previously applied) patch detected! Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file
drivers/md/raid6altivec.uc.rej
Reversed (or previously applied) patch detected! Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file fs/eventpoll.c.rej
failed. Clean up yourself.
David
next prev parent reply other threads:[~2005-03-15 16:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 6:05 Linux v2.6.8 Linus Torvalds
2004-08-14 10:10 ` Linux v2.6.8 - Oops on NFSv3 Willy Tarreau
2004-08-14 10:19 ` Willy Tarreau
2004-08-14 10:34 ` Jeff Garzik
2004-08-14 10:41 ` Linus Torvalds
2004-08-14 10:35 ` Willy Tarreau
2004-08-14 10:49 ` Linus Torvalds
2004-08-14 10:55 ` Christoph Hellwig
2004-08-14 11:05 ` Linus Torvalds
2004-08-14 11:18 ` Arjan van de Ven
2004-08-14 11:27 ` Jeff Garzik
2004-08-14 11:31 ` viro
2004-08-14 12:48 ` Nur Hussein
2004-08-14 20:57 ` Greg Norris
2004-08-18 20:57 ` [PATCH] scripts/patch-kernel: use EXTRAVERSION Randy.Dunlap
2004-08-22 20:40 ` Sam Ravnborg
2005-03-15 16:15 ` David Greaves [this message]
2005-03-15 16:25 ` [BUG] " Greg KH
2005-03-15 17:44 ` Greg KH
2005-03-15 17:54 ` Matt Mackall
2005-03-15 19:55 ` Sam Ravnborg
2005-03-15 18:02 ` David Greaves
2005-03-15 18:37 ` Sam Ravnborg
2005-04-12 0:07 ` [PATCH] scripts/patch-kernel: EXTRAVERSION patches are not incremental Randy.Dunlap
2004-08-17 3:13 ` Linux v2.6.8 - Oops on NFSv3 Patrick McFarland
2004-08-14 17:20 ` Matt Mackall
2004-08-15 20:10 ` Marcelo Tosatti
2004-08-16 3:37 ` Han Boetes
2004-08-16 14:06 ` Daniel Jacobowitz
2004-08-16 22:39 ` Bill Davidsen
2004-08-18 8:29 ` Robert Schwebel
2004-08-14 15:33 ` Norman Zhang
2004-08-14 10:19 ` [patch 2.6.8-rc4-mm1] via-velocity: wrong module name in Kconfig documentation Francois Romieu
2004-09-20 18:44 ` Jeff Garzik
2004-08-14 10:30 ` Linux v2.6.8 Jeff Garzik
2004-08-14 11:19 ` Stephan von Krawczynski
2004-08-14 11:38 ` Francois Romieu
2004-08-14 11:16 ` William Lee Irwin III
2004-08-16 17:56 ` Linux v2.6.8 (compile stats) John Cherry
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=42370A3A.6020206@dgreaves.com \
--to=david@dgreaves.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=haphazard@kc.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=sam@ravnborg.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