From: Mark Brown <broonie@kernel.org>
To: "Ondřej Jirman" <megi@xff.cz>,
linux-kernel@vger.kernel.org,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>, "Chen-Yu Tsai" <wens@csie.org>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Samuel Holland" <samuel@sholland.org>,
"Arnaud Ferraris" <arnaud.ferraris@collabora.com>,
linux-sound@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v3 0/4] Add support for jack detection to codec present in A64 SoC
Date: Tue, 26 Mar 2024 16:46:10 +0000 [thread overview]
Message-ID: <ebcae0f3-b5ac-4c1e-9a37-c7d58a564195@sirena.org.uk> (raw)
In-Reply-To: <2vhd45kylttgonosdcfn7ugwyy2vx56gijwf3ealz4tel65iqr@cs3kxrl6d2hh>
[-- Attachment #1: Type: text/plain, Size: 329 bytes --]
On Tue, Mar 26, 2024 at 05:33:14PM +0100, Ondřej Jirman wrote:
> Coincidentally, Intel kernel test bot found an issue today that this fails to
> build with CONFIG_SND_JACK_INPUT_DEV disabled. Should I send a followup fix or
> should I send v5 with the fix integrated into the patch that breaks?
Please send a followup.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-03-26 16:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 14:00 [PATCH v3 0/4] Add support for jack detection to codec present in A64 SoC Ondřej Jirman
2024-03-02 14:00 ` [PATCH v3 1/4] ASoC: sun50i-codec-analog: Move suspend/resume to set_bias_level Ondřej Jirman
2024-03-02 14:00 ` [PATCH v3 2/4] ASoC: sun8i-codec: Enable bus clock at STANDBY and higher bias Ondřej Jirman
2024-03-02 14:00 ` [PATCH v3 3/4] ASoC: sun50i-codec-analog: Enable jack detection on startup Ondřej Jirman
2024-03-02 14:00 ` [PATCH v3 4/4] ASoC: sun8i-codec: Implement jack and accessory detection Ondřej Jirman
2024-03-26 15:27 ` [PATCH v3 0/4] Add support for jack detection to codec present in A64 SoC Mark Brown
2024-03-26 16:33 ` Ondřej Jirman
2024-03-26 16:46 ` Mark Brown [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=ebcae0f3-b5ac-4c1e-9a37-c7d58a564195@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnaud.ferraris@collabora.com \
--cc=jernej.skrabec@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=megi@xff.cz \
--cc=perex@perex.cz \
--cc=samuel@sholland.org \
--cc=tiwai@suse.com \
--cc=wens@csie.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).