From: patchwork-bot+linux-arm-msm@kernel.org
To: Loic Poulain <loic.poulain@linaro.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v10 1/2] bus: mhi: Add mhi_queue_is_full function
Date: Tue, 29 Dec 2020 20:15:34 +0000 [thread overview]
Message-ID: <160927293455.13751.5750637902513749785.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1604424234-24446-1-git-send-email-loic.poulain@linaro.org>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Tue, 3 Nov 2020 18:23:53 +0100 you wrote:
> This function can be used by client driver to determine whether it's
> possible to queue new elements in a channel ring.
>
> Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> v1->v5: not part of the series
> v6: Add this commit, used for stopping TX queue
> v7: no change
> v8: remove static change (up to the compiler)
> v9: no change + Mani reviewed-by tag
> v10: no change
>
> [...]
Here is the summary with links:
- [v10,1/2] bus: mhi: Add mhi_queue_is_full function
https://git.kernel.org/qcom/c/d8c4a2236385
- [v10,2/2] net: Add mhi-net driver
https://git.kernel.org/qcom/c/3ffec6a14f24
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:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 17:23 [PATCH v10 1/2] bus: mhi: Add mhi_queue_is_full function Loic Poulain
2020-11-03 17:23 ` [PATCH v10 2/2] net: Add mhi-net driver Loic Poulain
2020-11-06 0:57 ` Jakub Kicinski
2020-11-06 0:57 ` [PATCH v10 1/2] bus: mhi: Add mhi_queue_is_full function Jakub Kicinski
2020-11-06 5:13 ` Manivannan Sadhasivam
2020-11-06 16:04 ` Jakub Kicinski
2020-11-06 16:28 ` Manivannan Sadhasivam
2020-11-06 16:39 ` Jakub Kicinski
2020-11-10 18:44 ` Kalle Valo
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=160927293455.13751.5750637902513749785.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=loic.poulain@linaro.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).