From: patchwork-bot+linux-remoteproc@kernel.org
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] remoteproc/mediatek: fix sparse errors
Date: Tue, 24 Nov 2020 04:20:06 +0000 [thread overview]
Message-ID: <160619160609.23996.9812608246907267637.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201116082537.3287009-1-tzungbi@google.com>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next):
On Mon, 16 Nov 2020 16:25:35 +0800 you wrote:
> Changes from v1:
> (https://patchwork.kernel.org/project/linux-arm-kernel/patch/20201116044121.2457272-1-tzungbi@google.com/)
> - separate into 2 patches
> - provide the line numbers in commit messages
>
> The series bases on https://git.kernel.org/pub/scm/linux/kernel/git/andersson/remoteproc.git/log/?h=for-next
>
> [...]
Here is the summary with links:
- [v2,1/2] remoteproc/mediatek: fix sparse errors on sram power on and off
https://git.kernel.org/andersson/remoteproc/c/778f2664fa34
- [v2,2/2] remoteproc/mediatek: fix sparse errors on dma_alloc and dma_free
https://git.kernel.org/andersson/remoteproc/c/903635cbc757
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-11-24 4:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 8:25 [PATCH v2 0/2] remoteproc/mediatek: fix sparse errors Tzung-Bi Shih
2020-11-16 8:25 ` [PATCH v2 1/2] remoteproc/mediatek: fix sparse errors on sram power on and off Tzung-Bi Shih
2020-11-16 8:42 ` Nicolas Boichat
2020-11-16 20:25 ` Mathieu Poirier
2020-11-16 8:25 ` [PATCH v2 2/2] remoteproc/mediatek: fix sparse errors on dma_alloc and dma_free Tzung-Bi Shih
2020-11-16 8:45 ` Nicolas Boichat
2020-11-16 20:32 ` Mathieu Poirier
2020-11-24 4:20 ` patchwork-bot+linux-remoteproc [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=160619160609.23996.9812608246907267637.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=tzungbi@google.com \
/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