From: Saalim Quadri <danascape@gmail.com>
To: krzysztof.kozlowski@linaro.org
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
danascape@gmail.com, daniel.baluta@nxp.com,
devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
robh+dt@kernel.org
Subject: Re: [PATCH] ASoC: dt-bindings: alc5632: Convert to dtschema
Date: Thu, 23 Mar 2023 22:41:11 +0530 [thread overview]
Message-ID: <20230323171111.17393-1-danascape@gmail.com> (raw)
In-Reply-To: <1a2e0f7a-771f-5590-fc54-b9dbf059a925@linaro.org>
Hello,
This is my first time using the Linux Kernel Mailing List. I apologise if I commit any mistakes.
> This should not be subsystem maintainer but someone related to the
> device. It's maintainer or interested contributor. Unless that's the
> case here?
yes it is wrong, he is not the subsystem maintainer. I will send the updated patch.
I have a doubt, for the maintainers list, is it required to include all the names of the subsystem maintainer
in the yaml too? As for this codec, there are 4, shall I include the names of all of them or the one to whom the
module is authored to?
Apologies,
Saalim
next prev parent reply other threads:[~2023-03-29 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 13:05 [PATCH] ASoC: dt-bindings: alc5632: Convert to dtschema Saalim Quadri
2023-03-23 15:15 ` Krzysztof Kozlowski
2023-03-23 17:11 ` Saalim Quadri [this message]
2023-03-23 19:08 ` Krzysztof Kozlowski
2023-03-23 19:17 ` Mark Brown
2023-03-23 19:37 ` [PATCH v2] " Saalim Quadri
2023-03-24 0:03 ` Mark Brown
2023-03-24 8:43 ` Krzysztof Kozlowski
2023-03-24 8:45 ` Krzysztof Kozlowski
2023-03-24 8:45 ` [PATCH] " Krzysztof Kozlowski
2023-03-25 16:36 ` [PATCH v2] " Saalim Quadri
2023-03-26 13:10 ` [PATCH v3] " Saalim Quadri
2023-03-26 14:46 ` Krzysztof Kozlowski
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=20230323171111.17393-1-danascape@gmail.com \
--to=danascape@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@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).