public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: linus.walleij@linaro.org, mika.westerberg@linux.intel.com,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	mallikarjunappa.sangannavar@intel.com, bala.senthil@intel.com
Subject: Re: [PATCH v2 0/2] Drop runtime PM support for Baytrail and Lynxpoint pinctrl
Date: Tue, 3 Oct 2023 15:31:55 +0300	[thread overview]
Message-ID: <ZRwJu23K1aEH5xsl@smile.fi.intel.com> (raw)
In-Reply-To: <20231003114036.27674-1-raag.jadav@intel.com>

On Tue, Oct 03, 2023 at 05:10:34PM +0530, Raag Jadav wrote:
> This series removes runtime PM support for the devices that are not
> explicitly attached to acpi_lpss_pm_domain as it is dead code anyway.
> 
> This has no functional impact and helps reduce their code and memory
> footprint.
> 
> bloat-o-meter:
> ==============
> 
> Baytrail:
> add/remove: 2/4 grow/shrink: 0/3 up/down: 49/-103 (-54)
> Total: Before=16104, After=16050, chg -0.34%
> 
> Lynxpoint:
> add/remove: 7/10 grow/shrink: 1/3 up/down: 152/-223 (-71)
> Total: Before=7506, After=7435, chg -0.95%

Pushed to my review and testing queue, thanks!

-- 
With Best Regards,
Andy Shevchenko



      parent reply	other threads:[~2023-10-03 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 11:40 [PATCH v2 0/2] Drop runtime PM support for Baytrail and Lynxpoint pinctrl Raag Jadav
2023-10-03 11:40 ` [PATCH v2 1/2] pinctrl: baytrail: drop runtime PM support Raag Jadav
2023-10-03 11:40 ` [PATCH v2 2/2] pinctrl: lynxpoint: " Raag Jadav
2023-10-03 12:16 ` [PATCH v2 0/2] Drop runtime PM support for Baytrail and Lynxpoint pinctrl Andy Shevchenko
2023-10-03 13:31   ` Raag Jadav
2023-10-03 13:43     ` Andy Shevchenko
2023-10-03 12:31 ` Andy Shevchenko [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=ZRwJu23K1aEH5xsl@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bala.senthil@intel.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mallikarjunappa.sangannavar@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=raag.jadav@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