All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stéphane ancelot" <sancelot@numalliance.com>
To: Romain Perier <romain.perier@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: rt patch
Date: Wed, 10 Jun 2015 08:58:33 +0200	[thread overview]
Message-ID: <5577E019.6030106@numalliance.com> (raw)
In-Reply-To: <CABgxDoJdNJMc3tE1=pzhP-=VsSB6irPT7q3_CPJpJJuGwSwRmA@mail.gmail.com>

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
patching file arch/arm/mm/highmem.c
patching file kernel/futex.c
patching file kernel/softirq.c
Hunk #1 FAILED at 461.
1 out of 1 hunk FAILED -- saving rejects to file kernel/softirq.c.rej
patching file arch/arm/include/asm/cmpxchg.h
patching file arch/arm/mm/fault.c
patching file kernel/printk/printk.c
patching file arch/x86/kvm/lapic.c
patching file arch/arm/kvm/arm.c
patching file arch/arm/kvm/psci.c
patching file arch/powerpc/include/asm/kvm_host.h
patching file arch/powerpc/kvm/book3s_hv.c
patching file arch/s390/include/asm/kvm_host.h
patching file arch/s390/kvm/interrupt.c
patching file arch/x86/kvm/lapic.c
Hunk #1 succeeded at 1539 (offset -34 lines).
Hunk #2 succeeded at 1553 (offset -34 lines).
patching file include/linux/kvm_host.h
patching file virt/kvm/async_pf.c
patching file virt/kvm/kvm_main.c
Hunk #2 succeeded at 1741 (offset 1 line).
Hunk #3 succeeded at 1758 (offset 1 line).
Hunk #4 succeeded at 1770 (offset 1 line).
Hunk #5 succeeded at 1879 (offset 1 line).
patching file kernel/locking/rtmutex.c
Hunk #1 FAILED at 1179.
1 out of 1 hunk FAILED -- saving rejects to file 
kernel/locking/rtmutex.c.rej
patching file include/linux/rwsem_rt.h
Hunk #1 FAILED at 20.
1 out of 1 hunk FAILED -- saving rejects to file 
include/linux/rwsem_rt.h.rej
patching file kernel/locking/rt.c
Hunk #1 FAILED at 316.
Hunk #2 FAILED at 327.
Hunk #3 FAILED at 356.
Hunk #4 FAILED at 371.
Hunk #5 FAILED at 396.
5 out of 5 hunks FAILED -- saving rejects to file kernel/locking/rt.c.rej
patching file include/linux/hrtimer.h
Reversed (or previously applied) patch detected!  Assume -R? [n]


On 10/06/2015 08:50, Romain Perier wrote:
> Hi,
>
> It would propably be easier for us if you give the error.... What is
> the exact error ?
>
> Regards,
> Romain
>
> 2015-06-10 8:44 GMT+02:00 Stéphane ancelot <sancelot@numalliance.com>:
>> Hi,
>>
>> Yes, I did ! This is why I asked ....
>> and kernels from here , why v3.0 and v4.0 kernels, patch errors .
>>
>> https://www.kernel.org/pub/linux/kernel/
>>
>>
>> Regards
>> S.Ancelot
>>
>>
>> On 09/06/2015 17:12, Romain Perier wrote:
>>>
>>> Hi,
>>>
>>> did you try the patches located at
>>> https://www.kernel.org/pub/linux/kernel/projects/rt/ ?
>>> Use the corresponding mainline kernel, for example if you want to use
>>> 3.18.13-rt10, download linux 3.18.13 (from torvald's repo for example)
>>> and apply the rt patch on it .
>>> Latest rt patches are for linux 3.18 and 4.0, so if you use the
>>> correct version it should work just fine.
>>>
>>> Everything is explained on the wiki,
>>> Regards,
>>> Romain
>>>
>>> 2015-06-09 16:47 GMT+02:00 Stéphane ancelot <sancelot@numalliance.com>:
>>>>
>>>> Hi,
>>>> I have tried the rt patches available on kernel.org.
>>>> Unfortunately none patches correctly with latests kernel !
>>>>
>>>> Where can I download the good ones ?
>>>> Regards,
>>>> Steph
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-rt-users"
>>>> in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-06-10  6:58 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 [this message]
2015-06-10 14:40         ` Joe Korty
     [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=5577E019.6030106@numalliance.com \
    --to=sancelot@numalliance.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=romain.perier@gmail.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.