From: Ruidong Tian <tianruidong@linux.alibaba.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: robert.moore@intel.com, rafael.j.wysocki@intel.com,
lenb@kernel.org, linux-acpi@vger.kernel.org,
acpica-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] ACPICA: AEST: Support AEST V2
Date: Fri, 12 Apr 2024 10:41:31 +0800 [thread overview]
Message-ID: <8ff4deab-13ab-4fdf-b418-fbfefe46c087@linux.alibaba.com> (raw)
In-Reply-To: <Zhep-UCqqPlg9BIh@bogus>
在 2024/4/11 17:14, Sudeep Holla 写道:
> On Thu, Apr 11, 2024 at 03:54:48PM +0800, Ruidong Tian wrote:
>>
>>
>> 在 2024/4/10 17:22, Sudeep Holla 写道:
>>> On Wed, Apr 10, 2024 at 02:36:00PM +0800, Ruidong Tian wrote:
>>>> AEST V2 was published[1], add V2 support based on AEST V1.
>>>>
>>>
>>> Any changes to ACPICA has to get merged in the external ACPICA project.
>>> Refer [1] for details from Rafael. You can also refer [2] in the kernel
>>> docs.
>>>
>>
>> Patch1 is just a fix to follow kernel code style.
>
> IIUC such changes are not allowed as ACPICA changes are always imported
> from the external project. So you have to take same route as patch2
In ACPICA, all struct use typedef which is not allowed in kernel:
It's a **mistake** to use typedef for structures and pointers[1].
I see all other structs in actbl2.h follow this rule, so I fix all
typedef in AEST struct to follow kernel code style. But i can not apple
this fix in ACPICA. Patch1 is just a kernel patch.
[1]: Documentation/process/coding-style.rst
> 1
>> Patch2 had merged to
>> acpica project, PR link can be see in patch2 comment:
>>
>> Link: https://github.com/acpica/acpica/commit/ebb4979
>
> Thanks, this will then get imported into kernel next time ACPICA changes
> get merged which usually happens regularly.
>
next prev parent reply other threads:[~2024-04-12 2:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 6:36 [PATCH v2 0/2] ACPICA: AEST: Support AEST V2 Ruidong Tian
2024-04-10 6:36 ` [PATCH v2 1/2] ACPICA: AEST: Fix coding style at struct definition Ruidong Tian
2024-04-10 6:36 ` [PATCH v2 2/2] ACPICA: AEST: Add support for the AEST V2 table Ruidong Tian
2024-04-22 16:50 ` Rafael J. Wysocki
2024-04-10 9:22 ` [PATCH v2 0/2] ACPICA: AEST: Support AEST V2 Sudeep Holla
2024-04-11 7:54 ` Ruidong Tian
2024-04-11 9:14 ` Sudeep Holla
2024-04-12 2:41 ` Ruidong Tian [this message]
2024-04-12 9:26 ` Sudeep Holla
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=8ff4deab-13ab-4fdf-b418-fbfefe46c087@linux.alibaba.com \
--to=tianruidong@linux.alibaba.com \
--cc=acpica-devel@lists.linux.dev \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=sudeep.holla@arm.com \
/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