public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: 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 v2 0/2] ACPI: LPSS: Prepare for SPI code cleanup
Date: Thu, 4 Apr 2024 15:11:28 +0300	[thread overview]
Message-ID: <Zg6Y8AVId_R83yMI@smile.fi.intel.com> (raw)
In-Reply-To: <20240404120856.4109303-1-andriy.shevchenko@linux.intel.com>

On Thu, Apr 04, 2024 at 03:06:57PM +0300, 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.
> 
> This patch series should go before
> https://lore.kernel.org/linux-acpi/20240403170302.1073841-1-andriy.shevchenko@linux.intel.com/

Indeliberately forgot
Reviewed-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>

(Code hasn't been changed, commit messages also stays the same, hence I added
 it from v1)

> In v2:
> - added Fixes tag to the first patch (Rafael)
> - reordered to get Fixes first in the series
> - v1: 20240402152952.3578659-1-andriy.shevchenko@linux.intel.com

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2024-04-04 12:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 12:06 [PATCH v2 0/2] ACPI: LPSS: Prepare for SPI code cleanup Andy Shevchenko
2024-04-04 12:06 ` [PATCH v2 1/2] ACPI: LPSS: Advertise number of chip selects via property Andy Shevchenko
2024-04-04 12:06 ` [PATCH v2 2/2] ACPI: LPSS: Remove nested ifdeffery for CONFIG_PM Andy Shevchenko
2024-04-04 12:11 ` Andy Shevchenko [this message]
2024-04-08 14:37   ` [PATCH v2 0/2] ACPI: LPSS: Prepare for SPI code cleanup 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=Zg6Y8AVId_R83yMI@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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