public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: bjdouma <bjdouma@xs4all.nl>
To: Yogesh Pahilwan <pahilwan.yogesh@spsoftindia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem while applying patch to 2.6.9 kernel
Date: Wed, 3 May 2006 20:01:12 +0200	[thread overview]
Message-ID: <20060503180112.GA23530@skyscraper.unix9.prv> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAvCUMqSY6jkeq1rIyy7sZ1cKAAAAQAAAAwZsyZCSXbUSO0mznjdzGqgEAAAAA@spsoftindia.com>

On Wed, May 03, 2006 at 05:32:02PM +0530, Yogesh Pahilwan wrote:
> I am facing some problem while applying patch to the 2.6.9 kernel.
> 
> I have done following to apply the patch:
> 
> # patch -p1 < ../../Patches/patch-ext3
> 
> But getting following things:
> 
> missing header for unified diff at line 3 of patch
> (Stripping trailing CRs from patch.)
> can't find file to patch at input line 3
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |#--- ../A_CLEAN_FILE_SYSTEM/jbd/commit.c       2006-02-25 11:43:19.000000000 -0600
> |#+++ commit.c  2006-03-29 20:53:29.000000000 -0600
> --------------------------
> File to patch:
> 
> Can anyone suggest what I am doing wrong while applying this patch or if the
> command is correct then why patch is giving the above errors.

You gotta lose the hash-mark at beginning-of-line of lines 1 and 2
(moise from some cut-n-paste operation?).  Then look at the second
line to see how many slashes you gotta skip (with -p -- looks like
it's -p0 here).

bjd

      parent reply	other threads:[~2006-05-03 18:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 12:02 Problem while applying patch to 2.6.9 kernel Yogesh Pahilwan
2006-05-03 12:11 ` Steven Rostedt
2006-05-03 12:32   ` Yogesh Pahilwan
2006-05-03 13:13     ` Steven Rostedt
2006-05-04 10:07     ` Florian Paul Schmidt
2006-05-03 12:33   ` Jesper Juhl
2006-05-03 18:01 ` bjdouma [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=20060503180112.GA23530@skyscraper.unix9.prv \
    --to=bjdouma@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pahilwan.yogesh@spsoftindia.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