All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georgi Djakov <djakov@kernel.org>
To: gregkh@linuxfoundation.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	djakov@kernel.org
Subject: [GIT PULL] interconnect fix for 5.18-rc
Date: Fri,  6 May 2022 11:59:23 +0300	[thread overview]
Message-ID: <20220506085923.23816-1-djakov@kernel.org> (raw)

Hello Greg,

This pull request contains one more fix for the current cycle. The
details are in the signed tag. It has been in linux-next during the
last few days. Please pull into char-misc-linus when possible.

Thanks,
Georgi

The following changes since commit 2fb251c265608636fc961b7d38e1a03937e57371:

  interconnect: qcom: sdx55: Drop IP0 interconnects (2022-04-14 09:47:16 +0300)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git tags/icc-5.18-rc6

for you to fetch changes up to 20ce30fb4750f2ffc130cdcb26232b1dd87cd0a5:

  interconnect: Restore sync state by ignoring ipa-virt in provider count (2022-05-03 22:24:21 +0300)

----------------------------------------------------------------
interconnect fixes for v5.18-rc

This contains an additional fix for sc7180 and sdx55 platforms that helps
them to enter suspend even on devices that don't have the most recent DT
changes.

- interconnect: Restore sync state by ignoring ipa-virt in provider count

Signed-off-by: Georgi Djakov <djakov@kernel.org>

----------------------------------------------------------------
Stephen Boyd (1):
      interconnect: Restore sync state by ignoring ipa-virt in provider count

 drivers/interconnect/core.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

             reply	other threads:[~2022-05-06  8:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  8:59 Georgi Djakov [this message]
2022-05-12  9:58 ` [GIT PULL] interconnect fix for 5.18-rc Georgi Djakov
2022-05-12 11:45   ` Greg KH
2022-05-13 14:16 ` Greg KH

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=20220506085923.23816-1-djakov@kernel.org \
    --to=djakov@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.