mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Daniel Scally <djrscally@gmail.com>
Subject: Re: [PATCH v1 1/1] software node: Update MAINTAINERS data base
Date: Tue, 4 Jan 2022 17:43:25 +0200	[thread overview]
Message-ID: <YdRrHRXYt5/8tAv1@smile.fi.intel.com> (raw)
In-Reply-To: <YcHHB82r7qT/yJmg@kuha.fi.intel.com>

On Tue, Dec 21, 2021 at 02:22:31PM +0200, Heikki Krogerus wrote:
> On Tue, Dec 21, 2021 at 09:14:09AM +0200, Andy Shevchenko wrote:
> > There are two updates to the MAINTAINERS regarding to software node API:
> > - add Dan Scally to be designated reviewer
> > - add rather tightly related device property files to the list
> > - adjust section name accordingly
> > 
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> Another way would be to have a separate entry for the unified device
> property API, and that could then have you (Andy), Sakari and Daniel
> as the reviers. I don't think I have much to say about those parts -
> I'm only interested in the software nodes. But it's up to you. FWIW:

Currently property.h shares information that is highly used by swnode.c.
I believe the current variant describes the state of affairs as is.

> Acked-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>

Thanks!

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2022-01-04 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21  7:14 Andy Shevchenko
2021-12-21  9:15 ` Daniel Scally
2021-12-21  9:16   ` Andy Shevchenko
2021-12-21  9:23     ` Daniel Scally
2021-12-21 11:54 ` Sakari Ailus
2021-12-21 13:31   ` Andy Shevchenko
2021-12-21 12:22 ` Heikki Krogerus
2022-01-04 15:43   ` Andy Shevchenko [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=YdRrHRXYt5/8tAv1@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=djrscally@gmail.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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

all inboxes | Powered by JetHome®