All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
	linux-fsdevel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Peter Zijlstra <peterz@infradead.org>,
	John Ogness <john.ogness@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH REPOST] fs/namespace: Boost the mount_lock.lock owner instead of spinning on PREEMPT_RT.
Date: Tue, 25 Jan 2022 16:49:37 +0100	[thread overview]
Message-ID: <20220125154937.zgmoybslcevaej5t@wittgenstein> (raw)
In-Reply-To: <YfAL0tu5P3T8s3rx@linutronix.de>

On Tue, Jan 25, 2022 at 03:40:18PM +0100, Sebastian Andrzej Siewior wrote:
> On 2021-11-26 14:24:14 [+0100], Christian Brauner wrote:
> > I thought you'd carry this in -rt, Sebastian and Thomas. So I've picked
> > this up and moved this into -next as we want it there soon so it can sit
> > there for as long as possible. I'll drop it if Al objects to the patch
> > or prefers to carry it.
> 
> It appears it missed -rc1. Did Al object to it or is this -rc2 material?

I didn't hear him object. I have it sitting in a separate tree [1] ready
to be sent. If I don't hear anything by the end of this week I'll send it!

[1]: https://git.kernel.org/pub/scm/linux/kernel/git/brauner/linux.git/log/?h=fs.fixes

Christian

  reply	other threads:[~2022-01-25 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 12:07 [PATCH REPOST] fs/namespace: Boost the mount_lock.lock owner instead of spinning on PREEMPT_RT Sebastian Andrzej Siewior
2021-11-26 13:24 ` Christian Brauner
2021-11-26 14:04   ` Sebastian Andrzej Siewior
2022-01-25 14:40   ` Sebastian Andrzej Siewior
2022-01-25 15:49     ` Christian Brauner [this message]
2022-01-25 16:46       ` Sebastian Andrzej Siewior
2022-02-08 14:07       ` Sebastian Andrzej Siewior

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=20220125154937.zgmoybslcevaej5t@wittgenstein \
    --to=brauner@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=christian.brauner@ubuntu.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    /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.