public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
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: Fri, 31 May 2024 09:31:09 +0200	[thread overview]
Message-ID: <87wmna1lqa.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240531093717.37c4ccf3@canb.auug.org.au>

On Fri, 31 May 2024 01:44:03 +0200,
Stephen Rothwell wrote:
> 
> Hi all,
> 
> In commit
> 
>   700fe6fd093d ("ALSA: seq: Fix yet another spot for system message conversion")
> 
> Fixes tag
> 
>   Fixes: c2bb79613fed ("ALSA: seq: Fix incorrect UMP type for system messages")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: edb32776196a ("ALSA: seq: Fix incorrect UMP type for system messages")

My bad, the old SHA ID was kept there after rebasing locally.
But since I've merged other stuff after this commit, I leave it as
is at this time.  The commit has another Fixes tag pointing to the
right commit, and this should enough for indicating for the stable
fixes.


thanks,

Takashi

  reply	other threads:[~2024-05-31  7:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 23:44 linux-next: Fixes tag needs some work in the sound-current tree Stephen Rothwell
2024-05-31  7:31 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-01 20:58 Stephen Rothwell
2024-04-02  5:56 ` Takashi Iwai
2021-06-02  7:09 Stephen Rothwell
2021-06-02  7:13 ` Dongliang Mu
2021-06-02  7:36 ` Takashi Iwai
2021-06-02  7:42   ` Dongliang Mu
2021-06-02  7:47     ` 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=87wmna1lqa.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox