linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Alleged fix for writer stall on -rcu branch dev
Date: Mon, 15 Apr 2019 12:41:50 +0200	[thread overview]
Message-ID: <20190415104150.zlpb4xarf757x5s2@linutronix.de> (raw)
In-Reply-To: <20190413181750.GA14850@linux.ibm.com>

On 2019-04-13 11:17:50 [-0700], Paul E. McKenney wrote:
> Oh, and probably more to the point...  I reviewed your patch, and with
> the subsequent changes it looks sane to me.  Plus the test failures thus
> far don't appear to have anything to do with your patch.  However, I am
> too cowardly to push this into the upcoming merge window, so I will do
> so on the one following (v5.3).

Thank you.

> 							Thanx, Paul

Sebastian

  reply	other threads:[~2019-04-15 10:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190409221426.GA11212@linux.ibm.com>
     [not found] ` <20190410181538.3ocva5lmh7ghrisr@linutronix.de>
     [not found]   ` <20190410184105.GR14111@linux.ibm.com>
     [not found]     ` <20190410191918.g2yqnsmuqukmzdfe@linutronix.de>
     [not found]       ` <20190410203302.GT14111@linux.ibm.com>
2019-04-11  0:06         ` Alleged fix for writer stall on -rcu branch dev Paul E. McKenney
2019-04-13 14:21           ` Paul E. McKenney
2019-04-13 18:17             ` Paul E. McKenney
2019-04-15 10:41               ` Sebastian Andrzej Siewior [this message]
2019-04-15 10:40             ` Sebastian Andrzej Siewior
2019-04-15 10:56               ` Paul E. McKenney
2019-04-15 11:04                 ` Sebastian Andrzej Siewior
2019-04-15 22:26                   ` Paul E. McKenney
2019-04-16  8:03                     ` Sebastian Andrzej Siewior
2019-04-23 15:25                   ` Sebastian Andrzej Siewior
2019-04-24  5:33                     ` Paul E. McKenney

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=20190415104150.zlpb4xarf757x5s2@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.ibm.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 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).