From: patchwork-bot+linux-arm-msm@kernel.org
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Some small cleanup/fixes for SPMI driver
Date: Tue, 29 Dec 2020 20:15:31 +0000 [thread overview]
Message-ID: <160927293131.13751.3142602682949729451.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1601360391.git.mchehab+huawei@kernel.org>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Tue, 29 Sep 2020 08:22:11 +0200 you wrote:
> Hi Stephen,
>
> While double-checking against yesterday's linux-next, I noticed
> that those two patches weren't merge yet.
>
> As you replied to both with your Reviewed-by:, are you expecting
> them to be merged via someone's tree, or are you intending
> to merge them via your tree?
>
> [...]
Here is the summary with links:
- [v2,1/2] spmi: get rid of a warning when built with W=1
https://git.kernel.org/qcom/c/b1f0aeecd25a
- [v2,2/2] spmi: fix some coding style issues at the spmi core
https://git.kernel.org/qcom/c/0be0a733c9cd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2020-12-29 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 6:22 [PATCH v2 0/2] Some small cleanup/fixes for SPMI driver Mauro Carvalho Chehab
2020-09-29 6:22 ` [PATCH v2 1/2] spmi: get rid of a warning when built with W=1 Mauro Carvalho Chehab
2020-11-13 20:47 ` Stephen Boyd
2020-09-29 6:22 ` [PATCH v2 2/2] spmi: fix some coding style issues at the spmi core Mauro Carvalho Chehab
2020-09-29 9:13 ` Marc Gonzalez
2020-11-13 20:47 ` Stephen Boyd
2020-10-02 21:22 ` [PATCH v2 0/2] Some small cleanup/fixes for SPMI driver Stephen Boyd
2020-10-03 10:56 ` Greg Kroah-Hartman
2020-10-14 21:26 ` Stephen Boyd
2020-10-15 12:55 ` Greg Kroah-Hartman
2020-12-29 20:15 ` 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=160927293131.13751.3142602682949729451.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=mchehab+huawei@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).