linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <robh@kernel.org>
Cc: <lgirdwood@gmail.com>, <broonie@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>, <perex@perex.cz>,
	<tiwai@suse.com>, <Nicolas.Ferre@microchip.com>,
	<alexandre.belloni@bootlin.com>, <alsa-devel@alsa-project.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] ASoC: dt-bindings: microchip: use proper naming syntax
Date: Tue, 13 Dec 2022 08:23:23 +0000	[thread overview]
Message-ID: <da11ec93-0d66-85f7-739d-ca48103d27ab@microchip.com> (raw)
In-Reply-To: <20221212173245.GA1171311-robh@kernel.org>

On 12.12.2022 19:32, Rob Herring wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Mon, Dec 12, 2022 at 06:41:50PM +0200, Claudiu Beznea wrote:
>> Use the following syntax for Microchip ASoC YAML files:
>> vendor,device.yaml
>>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
>> ---
>>  .../bindings/sound/mchp,i2s-mcc.yaml          | 108 ------------------
> 
> Deleting? Why? That's not what the commit message says.

Ah, I messed it up in v2... Will send v3.

> 
>>  ...,pdmc.yaml => microchip,sama7g5-pdmc.yaml} |   0
>>  ...rx.yaml => microchip,sama7g5-spdifrx.yaml} |   0
>>  ...tx.yaml => microchip,sama7g5-spdiftx.yaml} |   0
>>  4 files changed, 108 deletions(-)
>>  delete mode 100644 Documentation/devicetree/bindings/sound/mchp,i2s-mcc.yaml
>>  rename Documentation/devicetree/bindings/sound/{microchip,pdmc.yaml => microchip,sama7g5-pdmc.yaml} (100%)
>>  rename Documentation/devicetree/bindings/sound/{mchp,spdifrx.yaml => microchip,sama7g5-spdifrx.yaml} (100%)
>>  rename Documentation/devicetree/bindings/sound/{mchp,spdiftx.yaml => microchip,sama7g5-spdiftx.yaml} (100%)
> 
> These will all fail binding checks. You need to update the $id values.
> 
> Rob


  reply	other threads:[~2022-12-13  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 16:41 [PATCH v2 0/4] ASoC: microchip: power saving features and cleanups Claudiu Beznea
2022-12-12 16:41 ` [PATCH v2 1/4] ASoC: dt-bindings: microchip: use proper naming syntax Claudiu Beznea
2022-12-12 17:32   ` Rob Herring
2022-12-13  8:23     ` Claudiu.Beznea [this message]
2022-12-12 16:41 ` [PATCH v2 2/4] ASoC: mchp-pdmc: use runtime pm for clock power saving Claudiu Beznea
2022-12-12 16:41 ` [PATCH v2 3/4] ASoC: mchp-pdmc: add support for suspend to RAM Claudiu Beznea
2022-12-12 16:41 ` [PATCH v2 4/4] ASoC: mchp-spdiftx: use FIELD_PREP() where possible Claudiu Beznea

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=da11ec93-0d66-85f7-739d-ca48103d27ab@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).