From: "Kuppuswamy, Sathyanarayanan" <sathyanarayanan.kuppuswamy@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Erik Kaneda <erik.kaneda@intel.com>
Cc: Rafael J Wysocki <rjw@rjwysocki.net>, Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"open list:ACPI COMPONENT ARCHITECTURE (ACPICA)"
<devel@acpica.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v2 1/1] ACPICA: Add SVKL table headers
Date: Fri, 23 Apr 2021 09:52:07 -0700 [thread overview]
Message-ID: <df09a419-c881-c987-ef07-1b0e05bb171e@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0gH-Zg7YZPf9joaMt1zfYfNkUGpo596=9QEJ1NKAw87qQ@mail.gmail.com>
On 4/23/21 5:36 AM, Rafael J. Wysocki wrote:
> Evidently, this is ACPICA material, so I'm expecting to receive this
> patch from Erik within the normal ACPICA development process, so I'm
> not sure what the purpose of this submission is.
>
Erik already sent a pull request to merge this patch to ACPICA repo.
After he updated the ACPICA commit ID, he sent it to me for Linux
submission.
I am not sure whether there is a special process for ACPICA related
submission to Linux kernel. But if I had to guess, since I have sent
both SVKL and MADT patches at the same time, Erik might have assumed
that it should be merged in the same patch set and hence sent to me
for upstream submission.
> Has this patch been posted here for reference only?
If this submission is incorrect, I can request Erik to submit it again
for upstream merge.
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2021-04-23 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 21:49 [PATCH v2 1/1] ACPICA: Add SVKL table headers Kuppuswamy Sathyanarayanan
2021-04-23 12:36 ` Rafael J. Wysocki
2021-04-23 16:52 ` Kuppuswamy, Sathyanarayanan [this message]
2021-04-23 18:25 ` Rafael J. Wysocki
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=df09a419-c881-c987-ef07-1b0e05bb171e@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=devel@acpica.org \
--cc=erik.kaneda@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.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