From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH v1 0/2] ACPI: LPSS: Prepare for SPI code cleanup
Date: Tue, 2 Apr 2024 14:18:55 -0700 [thread overview]
Message-ID: <87797de2-7c10-4280-96c6-1e094762be69@linux.intel.com> (raw)
In-Reply-To: <20240402152952.3578659-1-andriy.shevchenko@linux.intel.com>
On 4/2/24 8:28 AM, Andy Shevchenko wrote:
> An ad-hoc cleanup followed by preparation for SPI code cleaning.
> The latter will be done in the next kernel cycle to avoid conflicts.
Looks good to me.
Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
> Andy Shevchenko (2):
> ACPI: LPSS: Remove nested ifdeffery for CONFIG_PM
> ACPI: LPSS: Advertise number of chip selects via property
>
> drivers/acpi/acpi_lpss.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
prev parent reply other threads:[~2024-04-02 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 15:28 [PATCH v1 0/2] ACPI: LPSS: Prepare for SPI code cleanup Andy Shevchenko
2024-04-02 15:28 ` [PATCH v1 1/2] ACPI: LPSS: Remove nested ifdeffery for CONFIG_PM Andy Shevchenko
2024-04-02 15:28 ` [PATCH v1 2/2] ACPI: LPSS: Advertise number of chip selects via property Andy Shevchenko
2024-04-04 10:58 ` Rafael J. Wysocki
2024-04-04 11:57 ` Andy Shevchenko
2024-04-02 18:58 ` [PATCH v1 0/2] ACPI: LPSS: Prepare for SPI code cleanup Andy Shevchenko
2024-04-02 21:18 ` Kuppuswamy Sathyanarayanan [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=87797de2-7c10-4280-96c6-1e094762be69@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=andriy.shevchenko@linux.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 \
/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