From: Daniel Scally <djrscally@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>
Subject: Re: [PATCH v1 1/1] software node: Update MAINTAINERS data base
Date: Tue, 21 Dec 2021 09:23:55 +0000 [thread overview]
Message-ID: <605c8f7b-599c-1644-686d-8b94d8f05e87@gmail.com> (raw)
In-Reply-To: <YcGbidqy+rgiY1vf@smile.fi.intel.com>
On 21/12/2021 09:16, Andy Shevchenko wrote:
> On Tue, Dec 21, 2021 at 09:15:30AM +0000, Daniel Scally wrote:
>> Morning
>>
>> On 21/12/2021 07:14, 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>
>>> ---
>>>
>>> Based on the latest Dan's involvement and amount of patches seen recently
>>> I went ahead and added his name to the list. Dan, please tell me if it's
>>> not appropriate.
>> This is fine by me - I don't know if you need a tag from me for this but
>> feel free to add whichever's appropriate
> Yep, please give a formal tag (usually Acked-by in this kind of cases).
>
Acked-by: Daniel Scally <djrscally@gmail.com>
next prev parent reply other threads:[~2021-12-21 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 7:14 [PATCH v1 1/1] software node: Update MAINTAINERS data base Andy Shevchenko
2021-12-21 9:15 ` Daniel Scally
2021-12-21 9:16 ` Andy Shevchenko
2021-12-21 9:23 ` Daniel Scally [this message]
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
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=605c8f7b-599c-1644-686d-8b94d8f05e87@gmail.com \
--to=djrscally@gmail.com \
--cc=andriy.shevchenko@linux.intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).