From: Hiraku Toyooka <hiraku.toyooka.gu@hitachi.com>
To: linux-rt-users@vger.kernel.org, tglx@linutronix.de,
mingo@elte.hu, bigeasy@linutronix.de,
Steven Rostedt <rostedt@goodmis.org>
Cc: "Sampath, Pradyumna" <pradyumna@hitachi.co.in>
Subject: Why isn't there individual CONFIG in CONFIG_PREEMPT_RT_FULL?
Date: Thu, 24 Oct 2013 21:43:14 +0900 [thread overview]
Message-ID: <526915E2.4040809@hitachi.com> (raw)
Hello,
I recently started to look at PREEMPT_RT patches(3.10.14-rt9) and I
have a question.
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_* ?
Best regards,
--
Hiraku TOYOOKA
Linux Technology Center
Yokohama Research Laboratory
Hitachi Ltd.
next reply other threads:[~2013-10-24 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 12:43 Hiraku Toyooka [this message]
2013-11-22 14:21 ` Why isn't there individual CONFIG in CONFIG_PREEMPT_RT_FULL? Sebastian Andrzej Siewior
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=526915E2.4040809@hitachi.com \
--to=hiraku.toyooka.gu@hitachi.com \
--cc=bigeasy@linutronix.de \
--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 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.