All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: rcu@vger.kernel.org, linux-kernel@vger.kernel.org, hch@lst.de
Subject: Re: [GIT PULL rcu/next] Supplementary RCU commits for 5.4
Date: Wed, 28 Aug 2019 19:48:05 +0200	[thread overview]
Message-ID: <20190828174805.GA77166@gmail.com> (raw)
In-Reply-To: <20190828172557.GA30541@linux.ibm.com>


* Paul E. McKenney <paulmck@kernel.org> wrote:

> Hello, Ingo,
> 
> This pull request contains the following changes:
> 
> 1.	A one-line change that affects only Tiny RCU that is needed
> 	by the RISC-V guys, courtesy of Christoph Hellwig.
> 
> 2.	An update to my email address.	The old one still works, at
> 	least most of the time.
> 
> All of these changes have been subjected to 0day Test Robot and -next
> testing, and are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
> 
> for you to fetch changes up to 049b405029c00f3fd9e4ffa269bdd29b429c4672:
> 
>   MAINTAINERS: Update from paulmck@linux.ibm.com to paulmck@kernel.org (2019-08-26 16:27:08 -0700)
> 
> ----------------------------------------------------------------
> Christoph Hellwig (1):
>       rcu: Don't include <linux/ktime.h> in rcutiny.h
> 
> Paul E. McKenney (1):
>       MAINTAINERS: Update from paulmck@linux.ibm.com to paulmck@kernel.org
> 
>  MAINTAINERS             | 14 +++++++-------
>  include/linux/rcutiny.h |  2 +-
>  2 files changed, 8 insertions(+), 8 deletions(-)

Pulled, thanks a lot Paul!

	Ingo

      reply	other threads:[~2019-08-28 17:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28 17:25 [GIT PULL rcu/next] Supplementary RCU commits for 5.4 Paul E. McKenney
2019-08-28 17:48 ` Ingo Molnar [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=20190828174805.GA77166@gmail.com \
    --to=mingo@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rcu@vger.kernel.org \
    /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.