From: Krzysztof Kozlowski <krzk@kernel.org>
To: Prasad Kumpatla <prasad.kumpatla@oss.qualcomm.com>,
Srinivas Kandagatla <srini@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-sound@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v1 3/3] arm64: defconfig: Enable Hawi LPASS LPI pinctrl driver
Date: Wed, 7 Oct 2026 09:45:49 +0200 [thread overview]
Message-ID: <1072f38f-8dd5-4e70-a583-c06e402ee90c@kernel.org> (raw)
In-Reply-To: <20261006053717.3455143-4-prasad.kumpatla@oss.qualcomm.com>
On 06/10/2026 07:37, Prasad Kumpatla wrote:
> Build the LPASS LPI pinctrl driver as module, as required by the Hawi
> and Maili platforms to control all the LPI GPIOs.
You already sent it two weeks ago, so this is not v1.
It wasn't picked up and this won't be either.
Same comments as for every other defconfig patches. Missing proper
description, missing rationale why. Hawi and Maili do not need that.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-07 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 5:37 [PATCH v1 0/3] ASoC: qcom: split out self-contained Hawi/Maili audio changes Prasad Kumpatla
2026-10-06 5:37 ` [PATCH v1 1/3] ASoC: codecs: wsa885x: Reset registers on teardown for B2B playback Prasad Kumpatla
2026-10-06 8:33 ` Ajay Kumar Nandam
2026-10-06 11:34 ` Prasad Kumpatla
2026-10-06 5:37 ` [PATCH v1 2/3] ASoC: qcom: sc8280xp: add Maili sound card configuration Prasad Kumpatla
2026-10-06 8:34 ` Ajay Kumar Nandam
2026-10-06 5:37 ` [PATCH v1 3/3] arm64: defconfig: Enable Hawi LPASS LPI pinctrl driver Prasad Kumpatla
2026-10-06 8:35 ` Ajay Kumar Nandam
2026-10-07 7:45 ` Krzysztof Kozlowski [this message]
2026-10-07 12:51 ` Prasad Kumpatla
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=1072f38f-8dd5-4e70-a583-c06e402ee90c@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=prasad.kumpatla@oss.qualcomm.com \
--cc=srini@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 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®