public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Ruidong Tian <tianruidong@linux.alibaba.com>
Cc: robert.moore@intel.com, rafael.j.wysocki@intel.com,
	lenb@kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
	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: Thu, 11 Apr 2024 10:14:33 +0100	[thread overview]
Message-ID: <Zhep-UCqqPlg9BIh@bogus> (raw)
In-Reply-To: <e3c91a7b-4bcc-45ce-92e6-c6a50ad80479@linux.alibaba.com>

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

> 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.

-- 
Regards,
Sudeep

  reply	other threads:[~2024-04-11  9:14 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 [this message]
2024-04-12  2:41       ` Ruidong Tian
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=Zhep-UCqqPlg9BIh@bogus \
    --to=sudeep.holla@arm.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=tianruidong@linux.alibaba.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