From: John <linux.kernel@free.fr>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, tglx@timesys.com,
John <linux.kernel@free.fr>
Subject: Re: 2.6.20-rt8 patch tweaked for 2.6.20.5
Date: Tue, 10 Apr 2007 18:22:34 +0200 [thread overview]
Message-ID: <461BB9CA.5010806@free.fr> (raw)
In-Reply-To: <20070410142302.GA1519@elte.hu>
Ingo Molnar wrote:
> John wrote:
>
>> Great! Can you tell me how you generate the original -rt patch, so I
>> can provide an updated version when a new 2.6.20 kernel is released?
>
> they should be generated the way you did: apply the 2.6.20 baseline -rt
> kernel patch to the later patches and fix up rejects. For later kernels
> just do the same.
What options do you give diff?
The output of your patch is e.g.
Index: linux/drivers/input/gameport/gameport.c
===================================================================
--- linux.orig/drivers/input/gameport/gameport.c
+++ linux/drivers/input/gameport/gameport.c
@@ -21,6 +21,7 @@
#include <linux/slab.h>
#include <linux/delay.h>
#include <linux/kthread.h>
+#include <linux/interrupt.h>
[...]
diff -upr gives me, e.g.
diff -upr linux-2.6.20.5/drivers/input/gameport/gameport.c
linux-2.6.20.5-rt8/drivers/input/gameport/gameport.c
--- linux-2.6.20.5/drivers/input/gameport/gameport.c 2007-04-06
12:44:59.000000000 +0200
+++ linux-2.6.20.5-rt8/drivers/input/gameport/gameport.c
2007-04-06 18:09:48.000000000 +0200
@@ -21,6 +21,7 @@
#include <linux/slab.h>
#include <linux/delay.h>
#include <linux/kthread.h>
+#include <linux/interrupt.h>
[...]
How do I get diff not to print the file time stamps?
How do I get diff not to print the command line for each file?
Regards.
prev parent reply other threads:[~2007-04-10 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 16:18 2.6.20-rt8 patch tweaked for 2.6.20.5 John
2007-04-06 17:36 ` Ingo Molnar
2007-04-10 9:07 ` John
2007-04-10 13:17 ` Ingo Molnar
2007-04-10 14:18 ` John
2007-04-10 14:23 ` Ingo Molnar
2007-04-10 16:22 ` John [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=461BB9CA.5010806@free.fr \
--to=linux.kernel@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@timesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.