linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Subject: Re: [PATCH] ACPI: PM: s2idle: More x86-specific code to the x86 directory
Date: Fri, 18 Dec 2020 14:31:07 +0530	[thread overview]
Message-ID: <3f18b469-69ec-0f3a-1714-a6b5f3f314b3@amd.com> (raw)
In-Reply-To: <1702151.Z2izUkvjaf@kreacher>



On 12/18/2020 12:53 AM, Rafael J. Wysocki wrote:
> [CAUTION: External Email]
> 
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> Some code in drivers/acpi/sleep.c (which is regarded as a generic
> file) related to suspend-to-idle support has grown direct dependencies
> on x86, but in fact it has been specific to x86 (which is the only
> user of it) anyway for a long time.
> 
> For this reason, move that code to a separate file under acpi/x86/
> and make it build and run as before under the right conditions.
> 
> While at it, rename a vendor checking function in that code and
> consistently use acpi_handle_debug() for printing debug-related
> information in it.
> 
> No expected functional impact.
> 
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Thank you Rafael.. This really helps!

      reply	other threads:[~2020-12-18  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 19:23 [PATCH] ACPI: PM: s2idle: More x86-specific code to the x86 directory Rafael J. Wysocki
2020-12-18  9:01 ` Shyam Sundar S K [this message]

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=3f18b469-69ec-0f3a-1714-a6b5f3f314b3@amd.com \
    --to=shyam-sundar.s-k@amd.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=srinivas.pandruvada@linux.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;
as well as URLs for NNTP newsgroup(s).