linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Jongepier <jeremy@autostatic.com>
To: linux-rt-users@vger.kernel.org
Subject: Re: Full RT kernel problem on arm
Date: Wed, 27 May 2015 21:34:50 +0200	[thread overview]
Message-ID: <55661C5A.2060705@autostatic.com> (raw)
In-Reply-To: <CAOn_9a4_CSEZb_fVVFRev+n4cT2CQKNLrgqaguMaRVaPSZ7zLQ@mail.gmail.com>

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

On 05/27/2015 07:25 PM, Warter wrote:
> It is interesting because if I use "Basic RT", there is no problem.

Then why not stick with that? A real-time kernel doesn't sound better as
far as I know ;)

Jeremy


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

      reply	other threads:[~2015-05-27 19:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 12:36 Full RT kernel problem on arm Warter
2015-05-27  7:10 ` Daniel Wagner
2015-05-27  7:33   ` Warter
2015-05-27 11:18     ` Daniel Wagner
2015-05-27 17:25       ` Warter
2015-05-27 19:34         ` Jeremy Jongepier [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=55661C5A.2060705@autostatic.com \
    --to=jeremy@autostatic.com \
    --cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).