From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
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: Sat, 17 Sep 2016 16:45:06 -0400 [thread overview]
Message-ID: <20160917204505.GP2513@windriver.com> (raw)
In-Reply-To: <1473313660.9698.38.camel@gmail.com>
[Re: [ANNOUNCE] 4.8-rc5-rt1 beta] On 08/09/2016 (Thu 07:47) Mike Galbraith wrote:
> 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.
I didn't see the patchlet, so I just did my own: https://goo.gl/MNiUy7
Let me know if anything looks wrong with it.
I also integrated the latest changes from Sebastian from the 4.6 branch
for this 4.8 repo; build tested btrfs and sanity boot tested the series
against 4.8-rc6 and pushed the changes out:
https://git.kernel.org/cgit/linux/kernel/git/paulg/4.8-rt-patches
Everything else is unchanged (incl. the NFS borkage below.)
Paul.
--
>
> > -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-17 20:45 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
2016-09-17 20:45 ` Paul Gortmaker [this message]
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=20160917204505.GP2513@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
/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.