public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: John <linux.kernel@free.fr>
Cc: linux-kernel@vger.kernel.org, tglx@timesys.com
Subject: Re: 2.6.20-rt8 patch tweaked for 2.6.20.5
Date: Fri, 6 Apr 2007 19:36:39 +0200	[thread overview]
Message-ID: <20070406173639.GA2929@elte.hu> (raw)
In-Reply-To: <461672D8.7090100@free.fr>


* John <linux.kernel@free.fr> wrote:

> Hello,
> 
> I've tweaked patch-2.6.20-rt8 so that it applies to 2.6.20.5
> 
> The unified diff is attached to this message.

thanks - this is useful to those who are not that much on the bleeding 
edge.

> I'd be happy to hear comments on what I've done wrong.
> 
> 78 hunks had to be offset and 3 hunks had to be fuzzed.
> 
> $ grep -B1 fuzz patch.log
> patching file arch/ia64/kernel/iosapic.c
> Hunk #3 succeeded at 469 with fuzz 2.
> --
> patching file kernel/fork.c
> Hunk #9 succeeded at 975 with fuzz 1.
> --
> patching file kernel/sched.c
> Hunk #46 succeeded at 3996 with fuzz 1.
> 
> What is the fuzz value, exactly?

it's harmless: when the 'patch' utility didnt find the 'context' of the 
patch chunk at its claimed position (because all patch chunks have 
precise coordinates of source code embedded), but finds them 'nearby' 
(or at least, somewhere in the file), it emits this reminder that the 
underlying code did change since the patch was generated. Generating a 
'clean' patch will get rid of these messages.

	Ingo

  reply	other threads:[~2007-04-06 17:36 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 [this message]
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

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=20070406173639.GA2929@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.kernel@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox