From: Daniel Carter <yass27106@gmail.com>
To: krzk@kernel.org, andersson@kernel.org, broonie@kernel.org,
srinivas.kandagatla@oss.qualcomm.com, konradybcio@kernel.org
Cc: robh@kernel.org, conor+dt@kernel.org, vkoul@kernel.org,
tiwai@suse.com, perex@perex.cz, lgirdwood@gmail.com,
pierre-louis.bossart@linux.dev, yung-chuan.liao@linux.intel.com,
abelvesa@kernel.org, linux-arm-msm@vger.kernel.org,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, yass27106@gmail.com
Subject: [PATCH v5 0/3] arm64: dts: qcom: add device tree for Asus Vivobook 16 X1607QA
Date: Mon, 16 Nov 2026 12:55:27 -0800 (PST) [thread overview]
Message-ID: <45f11591823b4395aa19dd3a3ee6dc90@gmail.com> (raw)
Hi Krzysztof, hi Srini, hi all,
v5 of the series, collecting the tags received on v4 and adding the
Cc: stable that Srini requested:
Changes since v4:
- dt-bindings patch 1/3: collected Krzysztof's Acked-by.
- soundwire patch 3/3: added Cc: stable@vger.kernel.org (as requested
for stable backporting given the Fixes: tags) and collected Srini's
Reviewed-by. No code changes in this patch.
- patch 2/3 is unchanged.
- The series is rebased onto v7.4-rc2. Patch 3/3 is functionally
identical to v4 (verified hunk-for-hunk); only its diff context
shifted, from the treewide devm_kmalloc_obj conversion that landed
in v7.4-rc2 for drivers/soundwire/qcom.c.
Series:
[1/3] dt-bindings: arm: qcom: document Asus Vivobook 16 X1607QA
[2/3] arm64: dts: qcom: add device tree for Asus Vivobook 16 X1607QA
[3/3] soundwire: qcom: check clk_prepare_enable() return values
Best regards,
Daniel Carter
next reply other threads:[~2026-11-16 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 20:55 Daniel Carter [this message]
2026-11-16 20:55 ` [PATCH v5 1/3] dt-bindings: arm: qcom: document Asus Vivobook 16 X1607QA Daniel Carter
2026-11-16 20:55 ` [PATCH v5 2/3] arm64: dts: qcom: add device tree for " Daniel Carter
2026-11-16 20:55 ` [PATCH v5 3/3] soundwire: qcom: check clk_prepare_enable() return values Daniel Carter
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=45f11591823b4395aa19dd3a3ee6dc90@gmail.com \
--to=yass27106@gmail.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk@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=pierre-louis.bossart@linux.dev \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@oss.qualcomm.com \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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