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: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>, 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-asoc tree
Date: Tue, 08 Apr 2025 14:18:59 +0200	[thread overview]
Message-ID: <87tt6yhmmk.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250408132729.78ce049a@canb.auug.org.au>

On Tue, 08 Apr 2025 05:27:29 +0200,
Stephen Rothwell wrote:
> 
> Hi all,
> 
> The following commit is also in the sound tree as a different commit
> (but the same patch):
> 
>   7288aa73e5cf ("ASoC: loongson: Replace deprecated PCI functions")
> 
> This is commit
> 
>   a81aca6f8ed8 ("ASoC: loongson: Replace deprecated PCI functions")
> 
> in the sound tree.

Yes, it's an oversight.  Since the doubly commits shouldn't bring too
much problem for this small change, we decided to keep as is.


thanks,

Takashi

  reply	other threads:[~2025-04-08 12:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  3:27 linux-next: duplicate patch in the sound-asoc tree Stephen Rothwell
2025-04-08 12:18 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-12  4:44 Stephen Rothwell
2024-09-12 11:07 ` Mark Brown
2024-09-12 12:08   ` Arnd Bergmann
2024-09-12 12:28     ` Arnd Bergmann
2024-01-04  3:11 Stephen Rothwell
2023-01-13  1:13 Stephen Rothwell
2023-01-20 15:52 ` Arnd Bergmann

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=87tt6yhmmk.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --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