From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: xen-devel@lists.xenproject.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [Xen-devel] [PATCH 1/3] arm/xen: don't inclide rwlock.h directly.1~B
Date: Thu, 26 Oct 2017 18:56:30 -0400 [thread overview]
Message-ID: <d2550965-8fc6-f9be-8d6e-8cc49a1d1c01@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1710051256230.3073@sstabellini-ThinkPad-X260>
On 10/05/2017 03:58 PM, Stefano Stabellini wrote:
> On Thu, 5 Oct 2017, Sebastian Andrzej Siewior wrote:
>> rwlock.h should not be included directly. Instead linux/splinlock.h
>> should be included. One thing it does is to break the RT build.
>>
>> Cc: Stefano Stabellini <sstabellini@kernel.org>
>> Cc: xen-devel@lists.xenproject.org
>> Cc: linux-arm-kernel@lists.infradead.org
>> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Applied to for-linus-4.14c.
-boris
prev parent reply other threads:[~2017-10-26 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 12:56 [PATCH 1/3] arm/xen: don't inclide rwlock.h directly Sebastian Andrzej Siewior
2017-10-05 12:56 ` [PATCH 2/3] greybus: audio: " Sebastian Andrzej Siewior
2017-10-05 15:17 ` Mark Greer
2017-10-05 12:56 ` [PATCH 3/3] xen/9pfs: " Sebastian Andrzej Siewior
2017-10-05 19:58 ` [PATCH 1/3] arm/xen: don't inclide rwlock.h directly.1~B Stefano Stabellini
2017-10-05 21:32 ` Sebastian Andrzej Siewior
2017-10-26 22:56 ` Boris Ostrovsky [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=d2550965-8fc6-f9be-8d6e-8cc49a1d1c01@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®