public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Free Ekanayaka <free@64studio.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Free Ekanayaka] Re: realtime-preempt and suspend2
Date: Sat, 14 Jan 2006 08:10:44 +1000	[thread overview]
Message-ID: <200601140810.44818.ncunningham@cyclades.com> (raw)
In-Reply-To: <87ek3c8279.fsf@miu-ft.org>

Hi.

On Saturday 14 January 2006 03:31, Free Ekanayaka wrote:
> Hi,
>
> I'm resending this email as for some reason it is not in the kernel ml
> archives, so I suspect it wasn't delivered properly..
>
> |--==> Nigel Cunningham writes:
>
>   NC> Hi.
>
>   NC> On Wednesday 11 January 2006 20:39, Free Ekanayaka wrote:
>   >>Hi,
>   >>
>   >>I'd like  to use both  the realtime-preempt  and the suspend2 patches,
>   >>but the seem to conflict in (I tried to apply them on 2.6.15).
>   >>
>   >>Did anybody experiment such combination?
>
>   NC> Give me more detail and I'll see if I can help.
>
> Thanks, the patch sequence is:
>
> 1) pristine kernel 2.6.15
> 2) suspend2 patch 2.2-rc16 (I used the apply script incl in the source
> tarball) [0] 3) realtime-preempt 2.6.15-rt2
>
> Of  course the  suspend2  patch applies happily,   but when I try with
> realtime-preempt I get some rejects, here is the log:
>
> http://people.miu-ft.org/~free/2.6.15+suspend2+rt.log

Thanks. I did see the message, but simply haven't had the time to get around 
to it yet. Thanks for the reminder.

Regards,

Nigel

  reply	other threads:[~2006-01-13 22:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-13 17:31 [Free Ekanayaka] Re: realtime-preempt and suspend2 Free Ekanayaka
2006-01-13 22:10 ` Nigel Cunningham [this message]
2006-01-13 22:42   ` Free Ekanayaka

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=200601140810.44818.ncunningham@cyclades.com \
    --to=ncunningham@cyclades.com \
    --cc=free@64studio.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox