All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Benjamin Li <benl@squareup.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Clean up MSM8939 interconnect driver
Date: Wed, 26 May 2021 19:03:24 +0000	[thread overview]
Message-ID: <162205580473.26840.15144099491699166407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210205015205.22947-1-benl@squareup.com>

Hello:

This series was applied to qcom/linux.git (refs/heads/for-next):

On Thu,  4 Feb 2021 17:52:03 -0800 you wrote:
> Following up on a review comment on commit 6c6fe5d3dc5e ("interconnect: qcom:
> Add MSM8939 interconnect provider driver") to clean up some log pollution.
> 
> This is based on icc-next (which appears to contain a refactor commonizing
> functions into icc-rpm.c).
> 
> v2:
> - Update commit message to add a full explanation, rather than referencing a
>   previous commit.
> 
> [...]

Here is the summary with links:
  - [v2,1/2] interconnect: qcom: icc-rpm: record slave RPM id in error log
    https://git.kernel.org/qcom/c/9b4ab638c49e
  - [v2,2/2] interconnect: qcom: msm8939: remove rpm-ids from non-RPM nodes
    https://git.kernel.org/qcom/c/7c911f9de7ab

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-05-26 19:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  1:52 [PATCH v2 0/2] Clean up MSM8939 interconnect driver Benjamin Li
2021-02-05  1:52 ` [PATCH v2 1/2] interconnect: qcom: icc-rpm: record slave RPM id in error log Benjamin Li
2021-02-05  1:52 ` [PATCH v2 2/2] interconnect: qcom: msm8939: remove rpm-ids from non-RPM nodes Benjamin Li
2021-02-05  3:03 ` [PATCH v2 0/2] Clean up MSM8939 interconnect driver Jun Nie
2021-05-26 19:03 ` patchwork-bot+linux-arm-msm [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=162205580473.26840.15144099491699166407.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=benl@squareup.com \
    --cc=linux-arm-msm@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.