From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: linuxball <linuxball@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH 1/1] 3.18.17-rt14 locktorture: Do NOT include rwlock.h directly
Date: Tue, 21 Jul 2015 18:45:27 +0200 [thread overview]
Message-ID: <20150721164527.GA21978@linutronix.de> (raw)
In-Reply-To: <55AE5517.9040403@gmail.com>
* linuxball | 2015-07-21 16:20:07 [+0200]:
>Including rwlock.h directly will cause kernel builds to fail
>if CONFIG_PREEMPT_RT_FULL is defined. The correct header file
>(rwlock_rt.h OR rwlock.h) will be included by spinlock.h which
>is included by locktorture.c anyway.
>
>Signed-off-by: Wolfgang M. Reimer <linuxball@gmail.com>
If you don't mind I set From: to you have here. If you intendent to sent
further patches I suggest that you get rid of "format=flowed" which adds
a white space for no reason to the diff. I won't fix it again.
Sebastian
prev parent reply other threads:[~2015-07-21 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 19:25 [ANNOUNCE] 3.18.17-rt14 Steven Rostedt
2015-07-20 9:33 ` [PATCH 1/1] 3.18.17-rt14 locktorture: Do NOT include rwlock.h directly linuxball
2015-07-20 15:47 ` Sebastian Andrzej Siewior
2015-07-21 14:20 ` linuxball
2015-07-21 16:45 ` 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=20150721164527.GA21978@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=linuxball@gmail.com \
--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).