All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Jeroen Van den Keybus <jeroen.vandenkeybus@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] [BUG] racy xnshadow_harden under CONFIG_PREEMPT
Date: Wed, 01 Feb 2006 13:34:41 +0100	[thread overview]
Message-ID: <43E0AAE1.6070600@domain.hid> (raw)
In-Reply-To: <fd6a47a90602010423k707ac91bm@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

Jeroen Van den Keybus wrote:
>> Revision 466 contains the mutex-info fix, but that is post -rc2. Why not
>> switching to SVN head?
> 
> 
> Philippe asked to apply the patch against Xenomai 2.1-rc2. Can I safely
> patch it against the SVN tree ? After that, what will 'svn up' do to the
> patched tree ?

The CONFIG_PREEMPT fix is already contained in the latest SVN revision,
no need to patch anymore.

When unsure if a patch will cleanly apply, try "patch --dry-run" first.
(Virtually) rejected hunks can then be used to asses if the patch fits -
without messing up the code base immediately.

> 
> Remember I'm quite new to Linux. Actually, I spent half an hour finding out
> how that patch stuff (especially the -p option) works.
> 

:) (it's no problem to ask even these kind of "stupid" questions to the
list or us directly - no one will bite you!)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2006-02-01 12:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 10:47 [Xenomai-core] [BUG] racy xnshadow_harden under CONFIG_PREEMPT Jan Kiszka
2006-01-21 10:51 ` [Xenomai-core] " Jeroen Van den Keybus
2006-01-21 16:47 ` [Xenomai-core] " Hannes Mayer
2006-01-21 17:01   ` Jan Kiszka
2006-01-22  8:10 ` Dmitry Adamushko
2006-01-22 16:19   ` Jeroen Van den Keybus
2006-01-23 18:22     ` Gilles Chanteperdrix
2006-01-23 19:16       ` Jan Kiszka
2006-01-30 14:51         ` Philippe Gerum
2006-01-30 15:33           ` Philippe Gerum
2006-01-30 16:01             ` Jan Kiszka
2006-01-30 23:10               ` Philippe Gerum
2006-01-31 19:01                 ` Jan Kiszka
2006-01-30 15:35           ` Philippe Gerum
2006-01-31 21:09             ` Jeroen Van den Keybus
2006-01-31 21:45               ` Philippe Gerum
2006-02-01  9:57                 ` Jeroen Van den Keybus
2006-02-01 10:03                   ` Jan Kiszka
2006-02-01 12:23                     ` Jeroen Van den Keybus
2006-02-01 12:34                       ` Jan Kiszka [this message]
2006-01-24 13:14       ` Dmitry Adamushko
2006-01-24 13:26         ` Jan Kiszka
2006-01-30 11:37           ` Dmitry Adamushko
2006-01-30 11:48             ` Jan Kiszka
2006-01-30 13:02               ` Dmitry Adamushko
2006-01-29 23:48 ` Philippe Gerum
2006-01-30 10:14   ` Philippe Gerum

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=43E0AAE1.6070600@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=jeroen.vandenkeybus@domain.hid \
    --cc=xenomai@xenomai.org \
    /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.