linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dongliang Mu <mudongliangabcd@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Takashi Iwai <tiwai@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the sound-current tree
Date: Wed, 2 Jun 2021 15:13:35 +0800	[thread overview]
Message-ID: <CAD-N9QVwA2+k82DRo1DvieXYXazdOwvBoerLtVBb4xrz=qwKSA@mail.gmail.com> (raw)
In-Reply-To: <20210602170946.37a2c6ec@canb.auug.org.au>

On Wed, Jun 2, 2021 at 3:09 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
>   b3531c648d87 ("ALSA: control led: fix memory leak in snd_ctl_led_register")
>
> Fixes tag
>
>   Fixes: a135dfb5de1 ("ALSA: led control - add sysfs kcontrol LED marking layer")
>
> has these problem(s):
>
>   - SHA1 should be at least 12 digits long
>
> This is probably not worth rebasing to fix, but can be avoided in the
> future 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").

:/ Sorry about this tag. The right SHA should be a135dfb5de15.

>
> --
> Cheers,
> Stephen Rothwell

  reply	other threads:[~2021-06-02  7:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  7:09 linux-next: Fixes tag needs some work in the sound-current tree Stephen Rothwell
2021-06-02  7:13 ` Dongliang Mu [this message]
2021-06-02  7:36 ` Takashi Iwai
2021-06-02  7:42   ` Dongliang Mu
2021-06-02  7:47     ` Takashi Iwai
2024-04-01 20:58 Stephen Rothwell
2024-04-02  5:56 ` Takashi Iwai

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='CAD-N9QVwA2+k82DRo1DvieXYXazdOwvBoerLtVBb4xrz=qwKSA@mail.gmail.com' \
    --to=mudongliangabcd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    /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).