From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Astrid Rost <astridr@axis.com>,
Astrid Rost <Astrid.Rost@axis.com>,
Mark Brown <broonie@kernel.org>, Dylan Reid <dgreid@chromium.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
kernel <kernel@axis.com>,
alsa-devel-mejlinglistan <alsa-devel@alsa-project.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: sound: ts3a227e: add control of debounce times
Date: Tue, 13 Sep 2022 11:13:50 +0200 [thread overview]
Message-ID: <404caabe-f855-012e-4cae-35abdb58f23a@linaro.org> (raw)
In-Reply-To: <bdfa3f29-f63d-1fb7-f37b-0b4a1f6374b3@axis.com>
On 13/09/2022 09:16, Astrid Rost wrote:
>
> Hello,
>
> I did the conversion from txt to YAML.
> It requests me to add as a maintainer?
>
> Dylan was the original Author.
The maintainer of the bindings should be a person caring about them and
about the hardware. Usually it is a person with some access to the
device or to its datasheet (but it's not a requirement). Feel free to
add yourself and/or Daniel and/or any current maintainer of the driver
(but not subsystem maintainer).
Best regards,
Krzysztof
prev parent reply other threads:[~2022-09-13 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 13:58 [PATCH] dt-bindings: sound: ts3a227e: add control of debounce times Astrid Rost
2022-09-08 12:20 ` Krzysztof Kozlowski
2022-09-08 14:35 ` Mark Brown
2022-09-09 7:16 ` Astrid Rost
2022-09-09 7:25 ` Krzysztof Kozlowski
2022-09-09 7:23 ` Krzysztof Kozlowski
2022-09-09 8:21 ` Krzysztof Kozlowski
2022-09-09 18:47 ` Mark Brown
2022-09-12 7:26 ` Astrid Rost
2022-09-13 7:16 ` Astrid Rost
2022-09-13 9:13 ` Krzysztof Kozlowski [this message]
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=404caabe-f855-012e-4cae-35abdb58f23a@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Astrid.Rost@axis.com \
--cc=alsa-devel@alsa-project.org \
--cc=astridr@axis.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@chromium.org \
--cc=kernel@axis.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).