From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH REPOST] rbtree: include rcu.h because we use it
Date: Wed, 9 May 2018 23:55:56 +0200 [thread overview]
Message-ID: <20180509215555.sihdfmijkx4nd6y2@linutronix.de> (raw)
In-Reply-To: <20180508160437.aa262315a98eaa0d3631bb27@linux-foundation.org>
On 2018-05-08 16:04:37 [-0700], Andrew Morton wrote:
> On Fri, 4 May 2018 12:31:59 +0200 Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>
> > Since commit c1adf20052d8 ("Introduce rb_replace_node_rcu()")
> > rbtree_augmented.h uses RCU related data structures but does not include
> > them. It works as long as gets somehow included before that and fails
> > otherwise.
>
> c1adf20052d8 was two years ago. Are there any actual real build errors
> arising from this? If so, backporting the patch might be needed?
I've seen them only in -RT. No backporting needed.
Sebastian
prev parent reply other threads:[~2018-05-09 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 10:31 [PATCH REPOST] rbtree: include rcu.h because we use it Sebastian Andrzej Siewior
2018-05-08 23:04 ` Andrew Morton
2018-05-09 21:55 ` 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=20180509215555.sihdfmijkx4nd6y2@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.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).