From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Banajit Goswami <bgoswami@quicinc.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, stable@vger.kernel.org
Subject: Re: [PATCH v4 2/4] ASoC: qcom: sc8280xp: limit speaker volumes
Date: Mon, 22 Jan 2024 18:29:12 +0100 [thread overview]
Message-ID: <Za6l6EP7OqXPU9mj@hovoldconsulting.com> (raw)
In-Reply-To: <aca2b125-acf8-4791-a3eb-ea19826d3ee4@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
On Mon, Jan 22, 2024 at 04:05:37PM +0000, Mark Brown wrote:
> On Mon, Jan 22, 2024 at 08:41:59AM +0100, Johan Hovold wrote:
> > On Mon, Jan 22, 2024 at 12:03:55AM +0000, Mark Brown wrote:
>
> > > This doesn't apply against current code, please check and resend.
>
> > These patches are based on Linus's tree after merging the sound updates
> > and I just verified that they apply cleanly to 6.8-rc1.
>
> > I couldn't find anything related in either linux-next or your ASoC tree
> > that should interfere.
>
> > Could you please try again or let me know which branch to rebase on?
>
> I was applying it against v6.8-rc1.
That's what I assumed, but I still don't understand why it doesn't apply
on your end:
$ git checkout -b tmp v6.8-rc1
$ b4 am 20240119112420.7446-1-johan+linaro@kernel.org
...
$ git am ./v4_20240119_johan_linaro_asoc_qcom_volume_fixes_and_codec_cleanups.mbx
Applying: ASoC: codecs: wsa883x: fix PA volume control
Applying: ASoC: qcom: sc8280xp: limit speaker volumes
Applying: ASoC: codecs: lpass-wsa-macro: fix compander volume hack
Applying: ASoC: codecs: wcd9335: drop unused gain hack remnant
And if I generate patches from this branch, the diffs are identical to
the v4 patches I sent.
Could you please try again, and tell me which patch fails to apply and
how it fails?
Johan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-01-22 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 11:24 [PATCH v4 0/4] ASoC: qcom: volume fixes and codec cleanups Johan Hovold
2024-01-19 11:24 ` [PATCH v4 1/4] ASoC: codecs: wsa883x: fix PA volume control Johan Hovold
2024-01-19 11:24 ` [PATCH v4 2/4] ASoC: qcom: sc8280xp: limit speaker volumes Johan Hovold
2024-01-19 15:26 ` Johan Hovold
2024-01-22 0:03 ` Mark Brown
2024-01-22 7:41 ` Johan Hovold
2024-01-22 16:05 ` Mark Brown
2024-01-22 17:29 ` Johan Hovold [this message]
2024-01-22 18:06 ` Mark Brown
2024-01-22 18:21 ` Johan Hovold
2024-01-19 11:24 ` [PATCH v4 3/4] ASoC: codecs: lpass-wsa-macro: fix compander volume hack Johan Hovold
2024-01-19 11:24 ` [PATCH v4 4/4] ASoC: codecs: wcd9335: drop unused gain hack remnant Johan Hovold
2024-01-22 21:54 ` [PATCH v4 0/4] ASoC: qcom: volume fixes and codec cleanups Mark Brown
2024-01-23 7:58 ` Johan Hovold
2024-01-23 13:05 ` Mark Brown
2024-01-23 13:30 ` Johan Hovold
2024-01-23 13:57 ` 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=Za6l6EP7OqXPU9mj@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=broonie@kernel.org \
--cc=johan+linaro@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.