linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 1/1] i2c: drivers: Use generic definitions for bus frequencies (part 2)
Date: Wed, 26 May 2021 19:03:25 +0000	[thread overview]
Message-ID: <162205580523.26840.8983397952617714168.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210331104622.84657-1-andriy.shevchenko@linux.intel.com>

Hello:

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

On Wed, 31 Mar 2021 13:46:22 +0300 you wrote:
> Since we have generic definitions for bus frequencies, let's use them.
> 
> Cc: Wolfram Sang <wsa@the-dreams.de>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Acked-by: Khalil Blaiech <kblaiech@nvidia.com>
> ---
> v2: added tag (Khalil), converted one missed place in DesignWare driver
>  drivers/i2c/busses/i2c-designware-master.c |  2 +-
>  drivers/i2c/busses/i2c-mlxbf.c             | 14 ++++----------
>  drivers/i2c/busses/i2c-qcom-cci.c          |  4 ++--
>  3 files changed, 7 insertions(+), 13 deletions(-)

Here is the summary with links:
  - [v2,1/1] i2c: drivers: Use generic definitions for bus frequencies (part 2)
    https://git.kernel.org/qcom/c/fd6ddaa0f50a

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: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 10:46 [PATCH v2 1/1] i2c: drivers: Use generic definitions for bus frequencies (part 2) Andy Shevchenko
2021-03-31 14:09 ` Robert Foss
2021-04-05 20:58 ` Wolfram Sang
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=162205580523.26840.8983397952617714168.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=andriy.shevchenko@linux.intel.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 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).