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 changes for 6.1
Date: Mon, 26 Sep 2022 16:53:01 +0300 [thread overview]
Message-ID: <20220926135301.28372-1-djakov@kernel.org> (raw)
Hello Greg,
This is the pull request with interconnect changes for the 6.1-rc1 merge
window. It contains some tiny updates. The details are in the signed tag.
All patches have been in linux-next. Please pull into char-misc-next when
possible.
Thanks,
Georgi
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git tags/icc-6.1-rc1
for you to fetch changes up to 7360d55ba1993cb59267507d04b7e62c40bad424:
Merge branch 'icc-ignore-return-val' into icc-next (2022-09-20 15:57:00 +0300)
----------------------------------------------------------------
interconnect changes for 6.1
These are the interconnect changes for the 6.1-rc1 merge window, which
this time are tiny. One is a series to convert the remove() callback of
platform devices to return void instead of int. The other change is
enabling modular support for a driver.
Signed-off-by: Georgi Djakov <djakov@kernel.org>
----------------------------------------------------------------
Georgi Djakov (1):
Merge branch 'icc-ignore-return-val' into icc-next
Huang Yiwei (1):
interconnect: qcom: Kconfig: Make INTERCONNECT_QCOM tristate
Uwe Kleine-König (8):
interconnect: imx: Ignore return value of icc_provider_del() in .remove()
interconnect: icc-rpm: Ignore return value of icc_provider_del() in .remove()
interconnect: icc-rpmh: Ignore return value of icc_provider_del() in .remove()
interconnect: msm8974: Ignore return value of icc_provider_del() in .remove()
interconnect: osm-l3: Ignore return value of icc_provider_del() in .remove()
interconnect: sm8450: Ignore return value of icc_provider_del() in .remove()
interconnect: Make icc_provider_del() return void
interconnect: imx: Make imx_icc_unregister() return void
drivers/interconnect/core.c | 10 +++-----
drivers/interconnect/imx/imx.c | 4 +--
drivers/interconnect/imx/imx.h | 2 +-
drivers/interconnect/imx/imx8mm.c | 4 ++-
drivers/interconnect/imx/imx8mn.c | 4 ++-
drivers/interconnect/imx/imx8mp.c | 4 ++-
drivers/interconnect/imx/imx8mq.c | 4 ++-
drivers/interconnect/qcom/Kconfig | 2 +-
drivers/interconnect/qcom/icc-common.c | 3 +++
drivers/interconnect/qcom/icc-rpm.c | 4 ++-
drivers/interconnect/qcom/icc-rpmh.c | 4 ++-
drivers/interconnect/qcom/msm8974.c | 4 ++-
drivers/interconnect/qcom/osm-l3.c | 4 ++-
drivers/interconnect/qcom/sm8450.c | 4 ++-
include/linux/interconnect-provider.h | 5 ++--
15 files changed, 39 insertions(+), 23 deletions(-)
next reply other threads:[~2022-09-26 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 13:53 Georgi Djakov [this message]
2022-09-26 17:27 ` [GIT PULL] interconnect changes for 6.1 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=20220926135301.28372-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 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).