soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Santosh Shilimkar <santosh.shilimkar@oracle.com>
Subject: Re: [GIT PULL 2/3] Drop pm_runtime_irq_safe() for smartreflex for v5.15
Date: Thu, 12 Aug 2021 10:54:56 +0300	[thread overview]
Message-ID: <YRTT0Oejj22qNAL+@atomide.com> (raw)
Message-ID: <20210812075456.ua7Lfr60FIpw3RrHkBMzPlJLytCaNtEBTubyEhk_9EE@z> (raw)
In-Reply-To: <pull-1628751694-126144@atomide.com-2>

Hi,

* Tony Lindgren <tony@atomide.com> [210812 07:04]:
> From: "Tony Lindgren" <tony@atomide.com>
> 
> The following changes since commit fdc07ca0724dd8ad00c22909a1464dc73ed6783e:
> 
>   Merge branch 'omap-for-v5.14/ti-sysc' into omap-for-v5.15/ti-sysc (2021-07-27 12:02:24 +0300)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.15/sr-signed
> 
> for you to fetch changes up to 74953a9136cfd650dd994daded520528f737b7b3:
> 
>   soc: ti: Remove pm_runtime_irq_safe() usage for smartreflex (2021-08-06 09:53:59 +0300)
> 
> ----------------------------------------------------------------
> Drop pm_runtime_irq_safe() usage for smartreflex for v5.15
> 
> We now have cleard pm_runtime_irq_safe() usage for all TI SoCs
> in Linux next except for smartreflex and 8250_omap. This change
> removes pm_runtime_irq_safe() usage for smartreflex, the
> 8250_omap depends on pending serial layer PM changes.

Looks like Santosh already queued up this patch and sent a pull request,
so my pull request for this change can be just ignored.

Regrds,

Tony


> ----------------------------------------------------------------
> Tony Lindgren (1):
>       soc: ti: Remove pm_runtime_irq_safe() usage for smartreflex
> 
>  drivers/bus/ti-sysc.c             |  6 ++---
>  drivers/soc/ti/smartreflex.c      | 52 +++++++++++++++++----------------------
>  include/linux/power/smartreflex.h |  2 ++
>  3 files changed, 26 insertions(+), 34 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-08-12  8:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-12  7:03 [GIT PULL 1/3] Two missed omap Kconfig patches for v5.15 Tony Lindgren
2021-08-12  7:03 ` Tony Lindgren
2021-08-12  7:03 ` [GIT PULL 2/3] Drop pm_runtime_irq_safe() for smartreflex " Tony Lindgren
2021-08-12  7:03   ` Tony Lindgren
2021-08-12  7:54   ` Tony Lindgren [this message]
2021-08-12  7:54     ` Tony Lindgren
2021-08-12 20:44   ` Arnd Bergmann
2021-08-12 20:44     ` Arnd Bergmann
2021-08-12  7:03 ` [GIT PULL 3/3] Changes for am3 cpsw and SanCloud " Tony Lindgren
2021-08-12  7:03   ` Tony Lindgren
2021-08-12 21:05   ` Arnd Bergmann
2021-08-12 21:05     ` Arnd Bergmann
2021-08-12 20:41 ` [GIT PULL 1/3] Two missed omap Kconfig patches " Arnd Bergmann
2021-08-12 20:41   ` Arnd Bergmann

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=YRTT0Oejj22qNAL+@atomide.com \
    --to=tony@atomide.com \
    --cc=arm@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=santosh.shilimkar@oracle.com \
    --cc=soc@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;
as well as URLs for NNTP newsgroup(s).