From: Frank Rowand <frowand.list@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Rob Herring <robh+dt@kernel.org>, Len Brown <lenb@kernel.org>,
devicetree@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] MAINTAINERS: device property: acpi: add fwnode.h
Date: Fri, 21 Jul 2017 15:33:05 -0700 [thread overview]
Message-ID: <59728121.2020508@gmail.com> (raw)
In-Reply-To: <2851122.8a0ts3VkAi@aspire.rjw.lan>
On 07/21/17 15:03, Rafael J. Wysocki wrote:
> On Thursday, July 20, 2017 12:13:24 PM frowand.list@gmail.com wrote:
>> From: Frank Rowand <frank.rowand@sony.com>
>>
>> ACPI is impacted by changes to fwnode.h, add a file entry
>> to ACPI
>>
>> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
>
> ACK for this one.
>
> Or do you want me to apply it?
Please apply it. So there won't be any conflicts between trees if
any other changes get made to this entry later in this cycle.
Thanks,
Frank
>
>> ---
>> MAINTAINERS | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 205d3977ac46..c0ac362e850a 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -302,6 +302,7 @@ S: Supported
>> F: drivers/acpi/
>> F: drivers/pnp/pnpacpi/
>> F: include/linux/acpi.h
>> +F: include/linux/fwnode.h
>> F: include/acpi/
>> F: Documentation/acpi/
>> F: Documentation/ABI/testing/sysfs-bus-acpi
>>
>
>
next prev parent reply other threads:[~2017-07-21 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 19:13 [PATCH 0/2] add fwnode.h to several MAINTAINERS entries frowand.list
2017-07-20 19:13 ` [PATCH 1/2] MAINTAINERS: device property: acpi: add fwnode.h frowand.list
2017-07-21 22:03 ` Rafael J. Wysocki
2017-07-21 22:33 ` Frank Rowand [this message]
2017-07-26 18:46 ` Rafael J. Wysocki
2017-07-20 19:13 ` [PATCH 2/2] MAINTAINERS: device property: of: " frowand.list
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=59728121.2020508@gmail.com \
--to=frowand.list@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@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