All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Korty <joe.korty@ccur.com>
To: St??phane ancelot <sancelot@numalliance.com>
Cc: Romain Perier <romain.perier@gmail.com>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: rt patch
Date: Wed, 10 Jun 2015 10:40:47 -0400	[thread overview]
Message-ID: <20150610144047.GB31886@zipoli.ccur.com> (raw)
In-Reply-To: <5577E019.6030106@numalliance.com>

On Wed, Jun 10, 2015 at 02:58:33AM -0400, St??phane ancelot wrote:
> here is an example with linux-3.18.13 and patch 3.18.13-rt10:
> 3.18.13-rt10
> 
> zcat ../patches-3.18.13-rt10.tar.gz |patch -p1 --dry-run
> patching file arch/arm64/kernel/perf_event.c
> Hunk #1 succeeded at 461 (offset -6 lines).
> patching file arch/sparc/Kconfig
> patching file arch/arm64/Kconfig
> Hunk #1 succeeded at 61 (offset -7 lines).
> patching file include/linux/notifier.h
> patching file include/linux/srcu.h
> patching file arch/x86/mm/iomap_32.c
> Hunk #1 FAILED at 65.
> 1 out of 1 hunk FAILED -- saving rejects to file arch/x86/mm/iomap_32.c.rej


It appears you are applying the patch to an Android or other third-party
derivative of Linux, instead of Linux proper, or that either the kernel
or the patch you have fetched is corrupt.  Try re-fetching everything and
try again.  This sequence works for me:

   cd
   mkdir junk
   cd junk
   wget -q ftp://ftp.kernel.org/pub/linux/kernel/v3.0/linux-3.18.11.tar.xz
   wget -q ftp://ftp.kernel.org/pub/linux/kernel/projects/rt/3.18/patch-3.18.13-rt10.patch.xz
   tar xf l*xz
   cd linux*11
   unxz <../pat*xz | patch -p1

There are some (annoying) offset errors, but no fuzzies or rejects like you have
been seeing.

Joe

  reply	other threads:[~2015-06-10 15:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 14:47 rt patch Stéphane ancelot
2015-06-09 15:12 ` Romain Perier
2015-06-10  6:44   ` Stéphane ancelot
2015-06-10  6:50     ` Romain Perier
2015-06-10  6:58       ` Stéphane ancelot
2015-06-10 14:40         ` Joe Korty [this message]
     [not found]           ` <00f101d0a394$d66f73a0$834e5ae0$@pont@sdcsystems.com>
2015-06-11  6:23             ` Stéphane ancelot
2015-06-11  8:19               ` Ralf Mardorf
2015-06-11  8:51                 ` Stéphane ancelot
2015-06-11  9:06                   ` Stéphane ancelot
2015-06-11 11:03                     ` Thomas Gleixner
2015-06-11 11:21                       ` Stéphane ancelot
2015-06-11 11:23                         ` Stéphane ancelot
2015-06-11 11:26                       ` Stéphane ancelot
2015-06-10 23:25         ` Thomas Gleixner
  -- strict thread matches above, loose matches on Subject: below --
2005-08-24 22:32 RT patch George Anzinger

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=20150610144047.GB31886@zipoli.ccur.com \
    --to=joe.korty@ccur.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=romain.perier@gmail.com \
    --cc=sancelot@numalliance.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.