All of lore.kernel.org
 help / color / mirror / Atom feed
From: Donald Hunter <donald.hunter@gmail.com>
To: Changwoo Min <changwoo@igalia.com>
Cc: Lukasz Luba <lukasz.luba@arm.com>,
	 linux-pm@vger.kernel.org, sched-ext@lists.linux.dev,
	 Jakub Kicinski <kuba@kernel.org>,
	 Network Development <netdev@vger.kernel.org>,
	 Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Concerns with em.yaml YNL spec
Date: Mon, 15 Dec 2025 10:51:01 +0000	[thread overview]
Message-ID: <m25xa8qaqy.fsf@gmail.com> (raw)
In-Reply-To: <5d3c37c0-d956-410d-83c8-24323d6f2aea@igalia.com>

Changwoo Min <changwoo@igalia.com> writes:

> Hi Donald,
>
> Thanks for the feedback. I rearranged a paragraph in the original email
> for easier reply.
>
> On 12/12/25 00:54, Donald Hunter wrote:
>> Hi,
>>
>> I guess the patch series was never cced to netdev or the YNL
>> maintainers so this is my first opportunity to review it.
>>
>
> You are right. I think I ran get_maintainer.pl only before adding
> em.yaml. That's my bad.
>
>> I just spotted the new em.yaml YNL spec that got merged in
>> bd26631ccdfd ("PM: EM: Add em.yaml and autogen files") as part of [1]
>> because it introduced new yamllint reports:
>> make -C tools/net/ynl/ lint
>> make: Entering directory '/home/donaldh/net-next/tools/net/ynl'
>> yamllint ../../../Documentation/netlink/specs
>> ../../../Documentation/netlink/specs/em.yaml
>>    3:1       warning  missing document start "---"  (document-start)
>>    107:13    error    wrong indentation: expected 10 but found 12  (indentation)
>>
>
> I will fix these lint warnings. Besides fixing those warnings, it would
> be useful to mention running lint somewhere. If there is a general
> guideline for adding a new netlink YAML, I will revise it in a separate
> patch.

I have a patch ready for the next merge window that adds a lint target.
For now you can run:

yamllint Documentation/netlink/specs

You're right, we don't have a guide for adding new netlink YAML but
that's something I should add to the series I have pending.

Thanks,
Donald.

      parent reply	other threads:[~2025-12-15 10:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 15:54 Concerns with em.yaml YNL spec Donald Hunter
2025-12-11 17:01 ` Andrew Lunn
2025-12-14 11:35   ` Changwoo Min
2025-12-14 16:21     ` Andrew Lunn
2025-12-15  1:57       ` Changwoo Min
2025-12-15 10:30         ` Rafael J. Wysocki
2025-12-15 15:01           ` Changwoo Min
2025-12-15 15:06             ` Rafael J. Wysocki
2025-12-16  2:06               ` Changwoo Min
2025-12-11 17:04 ` Andrew Lunn
2025-12-11 17:09   ` Donald Hunter
2025-12-11 17:47     ` Andrew Lunn
2025-12-14 11:14 ` Changwoo Min
2025-12-14 11:38   ` Changwoo Min
2025-12-15 10:51   ` Donald Hunter [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=m25xa8qaqy.fsf@gmail.com \
    --to=donald.hunter@gmail.com \
    --cc=changwoo@igalia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=sched-ext@lists.linux.dev \
    /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.