All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
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>,
	Qu Wenruo <wqu@suse.com>
Subject: Re: linux-next: Fixes tag needs some work in the btrfs tree
Date: Mon, 24 Feb 2020 15:37:20 +0100	[thread overview]
Message-ID: <20200224143720.GS2902@suse.cz> (raw)
In-Reply-To: <20200223133659.47fe9684@canb.auug.org.au>

On Sun, Feb 23, 2020 at 01:36:59PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   d461d8be723f ("btrfs: qgroup: Ensure qgroup_rescan_running is only set when the worker is at least queued")
> 
> Fixes tag
> 
>   Fixes: 8d9eddad194 (Btrfs: fix qgroup rescan worker initialization)
> 
> 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").

Patch with correct Fixes: tag has been merged as
81f7eb00ff5bb8326e82503a32809421d14abb8a, there was some duplication
with to-be-pulled branch and the development one, the latter with
the wrong formatting. Fixed in the next update.

  reply	other threads:[~2020-02-24 14:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23  2:36 linux-next: Fixes tag needs some work in the btrfs tree Stephen Rothwell
2020-02-24 14:37 ` David Sterba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-06 21:02 Stephen Rothwell
2022-11-10 21:24 ` Stephen Rothwell
2022-11-22 21:17 Stephen Rothwell
2022-11-23 12:09 ` David Sterba
2025-04-14 22:08 Stephen Rothwell
2025-04-15 18:43 ` David Sterba

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=20200224143720.GS2902@suse.cz \
    --to=dsterba@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=wqu@suse.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.