From: Thierry Reding <thierry.reding@gmail.com>
To: Svyatoslav Ryhel <clamor95@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
Maxim Schwalm <maxim.schwalm@gmail.com>,
Dmitry Osipenko <digetx@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v4 1/2] ARM: tegra: transformers: update WM8903 sound nodes
Date: Tue, 28 Mar 2023 13:21:10 +0200 [thread overview]
Message-ID: <ZCLNphF/bMRqcQEv@orome> (raw)
In-Reply-To: <20230327150219.13636-2-clamor95@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Mon, Mar 27, 2023 at 06:02:18PM +0300, Svyatoslav Ryhel wrote:
> - fix headset detection in common device tree;
> - use device GPIO mic detection on wm8903 transformers;
>
> Signed-off-by: Svyatoslav Ryhel <clamor95@gmail.com>
> ---
> arch/arm/boot/dts/tegra20-asus-tf101.dts | 13 +++++++------
> arch/arm/boot/dts/tegra30-asus-tf300t.dts | 6 ++----
> .../boot/dts/tegra30-asus-transformer-common.dtsi | 9 +++++----
> 3 files changed, 14 insertions(+), 14 deletions(-)
If you feel compelled to create a list of things you've changed in the
commit message, it often indicates that you should be creating separate
patches for each list item. Not a huge deal in this case because this
is all about fixing audio, but something to keep in mind for future
patches.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-28 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 15:02 [PATCH v4 0/2] Fix sound on ASUS Transformers Svyatoslav Ryhel
2023-03-27 15:02 ` [PATCH v4 1/2] ARM: tegra: transformers: update WM8903 sound nodes Svyatoslav Ryhel
2023-03-28 11:21 ` Thierry Reding [this message]
2023-03-27 15:02 ` [PATCH v4 2/2] ARM: tegra: transformers: bind RT5631 " Svyatoslav Ryhel
2023-03-28 11:21 ` [PATCH v4 0/2] Fix sound on ASUS Transformers Thierry Reding
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=ZCLNphF/bMRqcQEv@orome \
--to=thierry.reding@gmail.com \
--cc=clamor95@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maxim.schwalm@gmail.com \
--cc=robh+dt@kernel.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 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.