From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Pablo D. Bergamasco" <danpablo@gmail.com>
Cc: broonie@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzk+dt@kernel.org,
lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
linux-sound@vger.kernel.org, mgreer@animalcreek.com,
robh@kernel.org, vaibhav.sr@gmail.com
Subject: Re: [PATCH] dt-bindings: sound: add toshiba,apb-dummy-codec binding
Date: Thu, 18 Jun 2026 06:15:41 +0200 [thread overview]
Message-ID: <d5204b90-e37c-4b02-baea-0a1bec26e2c4@kernel.org> (raw)
In-Reply-To: <20260617145509.1782137-1-danpablo@gmail.com>
On 17/06/2026 16:55, Pablo D. Bergamasco wrote:
> On Wed, Jun 17, 2026, Krzysztof Kozlowski wrote:
>> Nope. We don't take bindings for staging. Isn't this documented in
>> staging docs already?
>
> I checked drivers/staging/greybus/Documentation/ and found only
> firmware and sysfs documentation. There is no existing DT binding
> documentation for the "toshiba,apb-dummy-codec" compatible string.
>
> Should I add the binding documentation within the staging directory
> itself, or is there a preferred approach for staging drivers?
We don't take bindings for staging drivers outside. I do not know if it
makes sense to have any bindings inside staging itself. Honestly it does
not matter to me.
You should not be fixing checkpatch warnings blindly.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-06-18 4:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 18:56 [PATCH] dt-bindings: sound: add toshiba,apb-dummy-codec binding Pablo D. Bergamasco
2026-06-16 20:23 ` Mark Brown
2026-06-17 10:50 ` Krzysztof Kozlowski
2026-06-17 14:55 ` Pablo D. Bergamasco
2026-06-18 4:15 ` 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=d5204b90-e37c-4b02-baea-0a1bec26e2c4@kernel.org \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=danpablo@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mgreer@animalcreek.com \
--cc=robh@kernel.org \
--cc=vaibhav.sr@gmail.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