[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0g8VeDG5KM8=Ls3m=Z+nRbCW6oP1ZoiLdz9rNW5-NSYTg@mail.gmail.com>
Date: Wed, 19 Apr 2017 21:34:57 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Cao jin <caoj.fnst@...fujitsu.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Robert Moore <robert.moore@...el.com>, Lv <lv.zheng@...el.com>,
Rafael Wysocki <rafael.j.wysocki@...el.com>,
Len Brown <lenb@...nel.org>
Subject: Re: [PATCH] acpi: fix typo
On Wed, Apr 19, 2017 at 7:21 AM, Cao jin <caoj.fnst@...fujitsu.com> wrote:
> Hi
>
> On 04/19/2017 08:20 AM, Rafael J. Wysocki wrote:
>> On Fri, Mar 31, 2017 at 11:46 AM, Cao jin <caoj.fnst@...fujitsu.com> wrote:
>>> Signed-off-by: Cao jin <caoj.fnst@...fujitsu.com>
>>> ---
>>> Documentation/acpi/linuxized-acpica.txt | 10 +++++-----
>>
>> Please send changes to this file separately.
>>
>>> include/acpi/actypes.h | 4 ++--
>>
>> This one belongs to ACPICA and there is a special process for
>> modifying ACPICA files.
>>
>
> I have read the process. So, does that means, we never send acpica patch
> to kernel mail list, they only can be sent to acpica project?
You can send them to linux-acpi, but then you need to CC the ACPICA
maintainers and development mailing list *and* make sure that the
patch modifies the ACPICA code only (ie. no mixed ACPICA and
non-ACPICA changes in one go, please).
Thanks,
Rafael
Powered by blists - more mailing lists