All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the rcu tree
Date: Thu, 13 Feb 2020 02:35:38 -0800	[thread overview]
Message-ID: <20200213103537.GX2935@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200213092613.1b66d1f5@canb.auug.org.au>

On Thu, Feb 13, 2020 at 09:26:13AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   71901ffaf70d ("locktorture: Print ratio of acquisitions, not failures")
> 
> Fixes tag
> 
>   Fixes: 0af3fe1e ("locktorture: Add a lock-torture kernel module")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
>     or later) just making sure it is not set (or set to "auto").

Good catch, will fix, thank you!

							Thanx, Paul

  reply	other threads:[~2020-02-13 10:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 22:26 linux-next: Fixes tag needs some work in the rcu tree Stephen Rothwell
2020-02-13 10:35 ` Paul E. McKenney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-28 22:10 Stephen Rothwell
2024-05-30 18:23 ` Paul E. McKenney
2024-04-08 23:14 Stephen Rothwell
2024-04-03 21:39 Stephen Rothwell
2024-04-04 12:14 ` Uladzislau Rezki
2024-04-04 14:35   ` Paul E. McKenney
2024-04-05 17:17     ` Uladzislau Rezki
2024-04-01 21:03 Stephen Rothwell
2023-04-05 22:36 Stephen Rothwell
2023-04-05 22:59 ` Paul E. McKenney
2020-10-05 11:53 Stephen Rothwell
2020-10-05 14:07 ` Paul E. McKenney
2019-12-11 20:44 Stephen Rothwell
2019-12-11 22:52 ` Paul E. McKenney
     [not found] <20191029075041.7bf3f723@canb.auug.org.au>
2019-10-28 21:01 ` Stephen Rothwell
2019-10-29  0:36   ` Paul E. McKenney
2019-10-28 20:48 Stephen Rothwell

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=20200213103537.GX2935@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.