From: "Alexey Klimov" <alexey.klimov@linaro.org>
To: "Mark Brown" <broonie@kernel.org>
Cc: <srinivas.kandagatla@linaro.org>, <quic_pkumpatl@quicinc.com>,
<a39.skl@gmail.com>, <quic_mohs@quicinc.com>,
<linux-sound@vger.kernel.org>, <krzysztof.kozlowski@linaro.org>,
<lgirdwood@gmail.com>, <perex@perex.cz>, <tiwai@suse.com>,
<dmitry.baryshkov@linaro.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/2] wcd937x codec fixes
Date: Fri, 01 Nov 2024 13:33:43 +0000 [thread overview]
Message-ID: <D5AVPVHDHG9A.ARDI8CYMPNCN@linaro.org> (raw)
In-Reply-To: <1995b110-ff67-48c3-9a82-c29a6a95a059@sirena.org.uk>
Hi Mark,
On Wed Oct 23, 2024 at 12:21 AM BST, Mark Brown wrote:
> On Tue, Oct 22, 2024 at 04:31:29AM +0100, Alexey Klimov wrote:
> > This sent as RFC because of the following:
> >
> > - regarding the LO switch patch. I've got info about that from two persons
> > independently hence not sure what tags to put there and who should be
> > the author. Please let me know if that needs to be corrected.
>
> The tags are fine there.
>
> Just as a general thing if two changes aren't directly related and don't
> overlap at all it's usually better to send them separately to avoid
> creating spurious dependencies which can slow down getting things
> reviewed and merged.
Thank you. Noted. Yes, they are technically independent. They were
somehow connected in my head, something like "both are needed to have
working audio with lesser troubles". I'll try to keep not related and
not overlapping things separated.
Best regards,
Alexey
next prev parent reply other threads:[~2024-11-01 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 3:31 [RFC PATCH 0/2] wcd937x codec fixes Alexey Klimov
2024-10-22 3:31 ` [RFC PATCH 1/2] ASoC: codecs: wcd937x: add missing LO Switch control Alexey Klimov
2024-10-22 3:31 ` [RFC PATCH 2/2] ASoC: codecs: wcd937x: relax the AUX PDM watchdog Alexey Klimov
2024-10-22 23:21 ` [RFC PATCH 0/2] wcd937x codec fixes Mark Brown
2024-11-01 13:33 ` Alexey Klimov [this message]
2024-10-29 20:35 ` 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=D5AVPVHDHG9A.ARDI8CYMPNCN@linaro.org \
--to=alexey.klimov@linaro.org \
--cc=a39.skl@gmail.com \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_mohs@quicinc.com \
--cc=quic_pkumpatl@quicinc.com \
--cc=srinivas.kandagatla@linaro.org \
--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