All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: tglx@linutronix.de, geert@linux-m68k.org,
	wangkefeng.wang@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL rcu/urgent] Fix printk format warning
Date: Wed, 3 Jun 2020 11:15:38 +0200	[thread overview]
Message-ID: <20200603091538.GA1360377@gmail.com> (raw)
In-Reply-To: <20200602155631.GA1638@paulmck-ThinkPad-P72>


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

> Hello!
> 
> This pull request contains a single commit that fixes a printk() format
> error that appears on 32-bit architectures.  This could be argued to
> be a minor bug, but it is a regression from this week's merge window,
> and is in code that is never used in production.  Therefore the risk of
> adding this late in process is quite low, more than worth it to fix the
> irritation/confusion that the bug can cause.
> 
> And a big "Thank you!!!" to Geert (CCed) for bringing this to my
> attention, as it has slipped through the cracks earlier.
> 
> The following changes since commit b1fcf9b83c4149c63d1e0c699e85f93cbe28e211:
> 
>   rcu: Provide __rcu_is_watching() (2020-05-19 15:51:21 +0200)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git urgent-for-mingo
> 
> for you to fetch changes up to b3e2d20973db3ec87a6dd2fee0c88d3c2e7c2f61:
> 
>   rcuperf: Fix printk format warning (2020-06-02 08:41:37 -0700)
> 
> ----------------------------------------------------------------
> Kefeng Wang (1):
>       rcuperf: Fix printk format warning
> 
>  kernel/rcu/rcuperf.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Pulled into tip:core/urgent, thanks Paul!

	Ingo

      reply	other threads:[~2020-06-03  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 15:56 [GIT PULL rcu/urgent] Fix printk format warning Paul E. McKenney
2020-06-03  9:15 ` 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=20200603091538.GA1360377@gmail.com \
    --to=mingo@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wangkefeng.wang@huawei.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.