From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] 4.8-rc5-rt1 beta
Date: Thu, 08 Sep 2016 07:47:40 +0200 [thread overview]
Message-ID: <1473313660.9698.38.camel@gmail.com> (raw)
In-Reply-To: <20160906182508.GB9950@windriver.com>
On Tue, 2016-09-06 at 14:25 -0400, Paul Gortmaker wrote:
> Patch conflicts/issues of interest 4.6 --> 4.7
> ----------------------------------------------
>
> -v4.7 introduced a lot of users of down_write_killable which wasn't
> implemented for -rt (rwsem_rt.h), so I created one. (see new patch
> rt-create-down_write_killable.patch -- local commit 14625e96ff085f),
> it probably warrants a look see from other people smarter than me.
You forgot nested, so btrfs won't build. I posted a patchlet here that
includes it.
> -Al Viro added a 2nd user of down_read_non_owner into NFS unlink.
> Previously it was just bcache and Sebastian just made that depend on
> !RT_FULL (md-disable-bcache.patch). So we'll need to decide what to
> with that; I just ignored NFS for now, since it is horrible anyway.
> (see upstream commit 884be175351e73c)
Yeah, that is annoying. I've been carrying a revert ever since, with
poke nfs on todo, but it seems to be marooned there (haven't even
gotten around to generating the first obligatory explosion).
-Mike
next prev parent reply other threads:[~2016-09-08 6:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 18:25 [ANNOUNCE] 4.8-rc5-rt1 beta Paul Gortmaker
2016-09-08 5:47 ` Mike Galbraith [this message]
2016-09-17 20:45 ` Paul Gortmaker
2016-10-02 23:35 ` Paul Gortmaker
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=1473313660.9698.38.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.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