From: Conor Dooley <conor@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Mark Brown <broonie@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Hal Feng <hal.feng@starfivetech.com>,
Xingyu Wu <xingyu.wu@starfivetech.com>,
Walker Chen <walker.chen@starfivetech.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: defconfig: Remove CONFIG_SND_SOC_STARFIVE=m
Date: Wed, 9 Jul 2025 17:12:34 +0100 [thread overview]
Message-ID: <20250709-gem-disparity-185256a670f0@spud> (raw)
In-Reply-To: <CAMuHMdVwbHoEbjC2y4kpJuhx7CYsRxO9Y+eCUhJkKogk=zDs8w@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]
On Wed, Jul 09, 2025 at 11:29:24AM +0200, Geert Uytterhoeven wrote:
> Hi Conor,
>
> On Tue, 8 Jul 2025 at 18:49, Conor Dooley <conor@kernel.org> wrote:
> > From: Conor Dooley <conor.dooley@microchip.com>
> >
> > On Tue, 08 Jul 2025 17:36:48 +0200, Geert Uytterhoeven wrote:
> > > The SND_SOC_STARFIVE Kconfig symbol was removed, but it is still enabled
> > > in the RISC-V defconfig. Just remove it, as it is no longer needed.
> >
> > As I mentioned to Palmer a few mins ago, I'll grab this along with a
> > couple other soc-related defconfig patches I have. (Apologies if this
> > goes out twice, I got a warning last time about a timeout, so ending again)
> >
> > [1/1] riscv: defconfig: Remove CONFIG_SND_SOC_STARFIVE=m
> > https://git.kernel.org/conor/c/493e9b085299
>
> Sorry, I forgot to mention that the commit my patch fixes is only in
> the sound tree. One other patch in the original series did include a
> defconfig update for a MIPS platform, so it may be more appropriate
> for Mark to include it. Or just wait for v6.17 ;-)
I was going to include it in 6.17 material, with the other soc-related
defconfig bits. I'll drop it if it's problematic of course.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-07-09 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 15:36 [PATCH] riscv: defconfig: Remove CONFIG_SND_SOC_STARFIVE=m Geert Uytterhoeven
2025-07-08 16:48 ` Conor Dooley
2025-07-08 17:56 ` Palmer Dabbelt
2025-07-09 9:29 ` Geert Uytterhoeven
2025-07-09 16:12 ` Conor Dooley [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=20250709-gem-disparity-185256a670f0@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=hal.feng@starfivetech.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=walker.chen@starfivetech.com \
--cc=xingyu.wu@starfivetech.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