mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Donald Hunter <donald.hunter@gmail.com>
Cc: Changwoo Min <changwoo@igalia.com>,
	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: Thu, 11 Dec 2025 18:47:16 +0100	[thread overview]
Message-ID: <8a0dbc9d-0ed4-4a4c-8b5d-5779d07761a2@lunn.ch> (raw)
In-Reply-To: <CAD4GDZxYVwzxHBRnpG1RnkaD3wPW+-GUozhBg7hzO-_3X_PPpA@mail.gmail.com>

> It is covered by the Documentation/netlink/ entry:
> 
> ./scripts/get_maintainer.pl Documentation/netlink/specs/em.yaml
> Lukasz Luba <lukasz.luba@arm.com> (maintainer:ENERGY MODEL)
> "Rafael J. Wysocki" <rafael@kernel.org> (maintainer:ENERGY MODEL)
> Donald Hunter <donald.hunter@gmail.com> (maintainer:YAML NETLINK (YNL))
> Jakub Kicinski <kuba@kernel.org> (maintainer:YAML NETLINK (YNL))

Yep. So it should of gone flying passed on the netdev list.

But it did not:

https://lore.kernel.org/all/20251014001055.772422-4-changwoo@igalia.com/

Very little of what get_maintainers suggest should be in Cc: is
actually in Cc: :-(

	Andrew

  reply	other threads:[~2025-12-11 17:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 15:54 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 [this message]
2025-12-14 11:14 ` Changwoo Min
2025-12-14 11:38   ` Changwoo Min
2025-12-15 10:51   ` Donald Hunter

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=8a0dbc9d-0ed4-4a4c-8b5d-5779d07761a2@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=changwoo@igalia.com \
    --cc=donald.hunter@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®