From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
Cc: linux-rt-users@vger.kernel.org, tglx@linutronix.de,
mingo@elte.hu, Steven Rostedt <rostedt@goodmis.org>,
"Sampath, Pradyumna" <pradyumna@hitachi.co.in>
Subject: Re: Why isn't there individual CONFIG in CONFIG_PREEMPT_RT_FULL?
Date: Fri, 22 Nov 2013 15:21:00 +0100 [thread overview]
Message-ID: <20131122142100.GB8698@linutronix.de> (raw)
In-Reply-To: <526915E2.4040809@hitachi.com>
* Hiraku Toyooka | 2013-10-24 21:43:14 [+0900]:
>Hello,
Hello
>CONFIG_PREEMPT_RT_FULL consists of many patches. I think it doesn't
>represent specific feature but is general term of various features.
>Why don't those features have each CONFIG_* ?
Do you have something in particular in mind?
As long as it makes sense, there are CONFIG_* introduced. If a patch
breaks locks for instance then we don't a special CONFIG item because
this what we need and we don't keep both versions around (and the non-RT
variant can work both ways).
>Best regards,
Sebastian
prev parent reply other threads:[~2013-11-22 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 12:43 Why isn't there individual CONFIG in CONFIG_PREEMPT_RT_FULL? Hiraku Toyooka
2013-11-22 14:21 ` Sebastian Andrzej Siewior [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=20131122142100.GB8698@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=hiraku.toyooka.gu@hitachi.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pradyumna@hitachi.co.in \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).