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: duplicate patch in the sound tree
Date: Fri, 04 Oct 2024 09:00:53 +0200	[thread overview]
Message-ID: <87y134mjx6.wl-tiwai@suse.de> (raw)
In-Reply-To: <20241004123417.2dea135f@canb.auug.org.au>

On Fri, 04 Oct 2024 04:34:17 +0200,
Stephen Rothwell wrote:
> 
> Hi all,
> 
> The following commit is also in the sound-current tree as a different
> commit (but the same patch):
> 
>   3e8800273c4b ("ALSA: hda: Add missing parameter description for snd_hdac_stream_timecounter_init()")
> 
> This is commit
> 
>   740986edaf2d ("ALSA: hda: Add missing parameter description for snd_hdac_stream_timecounter_init()")
> 
> in the sound-current tree.

Fixed now, thanks for noticing.


Takashi

      reply	other threads:[~2024-10-04  7:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04  2:34 linux-next: duplicate patch in the sound tree Stephen Rothwell
2024-10-04  7:00 ` Takashi Iwai [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=87y134mjx6.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