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.10
Date: Fri, 3 May 2024 13:19:01 +0300 [thread overview]
Message-ID: <20240503101901.1681356-1-djakov@kernel.org> (raw)
Hello Greg,
This is the pull request with interconnect changes for the v6.10-rc1 merge
window. It contains tiny clean-up and fix. As always, the summary is
in the signed tag.
The patches have been in linux-next for more than a week with no reported
issues. Please pull into char-misc-next when possible.
Thanks,
Georgi
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/djakov/icc.git tags/icc-6.10-rc1
for you to fetch changes up to 230d05b1179f6ce6f8dc8a2b99eba92799ac22d7:
interconnect: qcom: qcm2290: Fix mas_snoc_bimc QoS port assignment (2024-04-11 20:46:26 +0300)
----------------------------------------------------------------
interconnect changes for 6.10
This pull request contains the interconnect changes for the 6.10-rc1 merge
window. It contains some small driver changes listed below:
Driver changes:
- Cleanup sm6115 QoS port numbering.
- Fix incorrect port value in qcm2290 driver.
Signed-off-by: Georgi Djakov <djakov@kernel.org>
----------------------------------------------------------------
Konrad Dybcio (2):
interconnect: qcom: sm6115: Unspaghettify SNoC QoS port numbering
interconnect: qcom: qcm2290: Fix mas_snoc_bimc QoS port assignment
drivers/interconnect/qcom/qcm2290.c | 2 +-
drivers/interconnect/qcom/sm6115.c | 33 ++++----
2 files changed, 19 insertions(+), 16 deletions(-)
next reply other threads:[~2024-05-03 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 10:19 Georgi Djakov [this message]
2024-05-04 7:48 ` [GIT PULL] interconnect changes for 6.10 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=20240503101901.1681356-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 read-only IMAP folder(s) and NNTP newsgroup(s).