mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jau@free.fr
To: Mark Brown <broonie@kernel.org>
Cc: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
	 Liam Girdwood <lgirdwood@gmail.com>,
	 Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	 alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: sti: add missing probe entry for player and reader
Date: Mon, 22 Jul 2024 14:31:24 +0200 (CEST)	[thread overview]
Message-ID: <1474761635.17820466.1721651484902.JavaMail.root@zimbra60-e10.priv.proxad.net> (raw)
In-Reply-To: <d85590f2-88b3-4bc2-b7b8-9f96a5d5bb17@sirena.org.uk>

Thanks for the review!

See updated changlog, if ok for you, I will send a V2

Le 22/07/2024 12:52, Mark Brown a écrit :
> This should be in the changelog, your actual changelog doesn't describe
> the actual change at all.
> 

New Changelog:

  This patch addresses a regression in the ASoC STI drivers that was introduced in Linux version 6.6.y.
  The issue originated from a series of patches (see https://lore.kernel.org/all/87wmy5b0wt.wl-kuninori.morimoto.gx@renesas.com/)
  that unintentionally omitted necessary probe functions for the player and reader components.

  Probe function in `sound/soc/sti/sti_uniperif.c:415` is being replaced by another probe function located at 
  `sound/soc/sti/sti_uniperif.c:453`, which should instead be derived from the player and reader components.
  This patch correctly reinserts the missing probe entries, restoring the intended functionality.

> This detail isn't really needed, it just describes the content of the
> patch.

ok, I remove this part.

Regards, 
Jérôme

  reply	other threads:[~2024-07-22 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 15:40 Jerome Audu
2024-07-22 10:52 ` Mark Brown
2024-07-22 12:31   ` jau [this message]
2024-08-14 17:12     ` Mark Brown

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=1474761635.17820466.1721651484902.JavaMail.root@zimbra60-e10.priv.proxad.net \
    --to=jau@free.fr \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®