From: patchwork-bot+linux-remoteproc@kernel.org
To: Suman Anna <s-anna@ti.com>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v2 0/3] PRU firmware event/interrupt mapping fixes
Date: Wed, 14 Apr 2021 02:20:10 +0000 [thread overview]
Message-ID: <161836681090.7360.10429412919501045588.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210407155641.5501-1-s-anna@ti.com>
Hello:
This series was applied to andersson/remoteproc.git (refs/heads/for-next):
On Wed, 7 Apr 2021 10:56:38 -0500 you wrote:
> Hi All,
>
> The following is a minor revised version of the series [1] that includes fixes
> for various different issues associated with the PRU firmware event/interrupt
> mapping configuration logic. Please see the v1 cover-letter [1] for additional
> details.
>
> [...]
Here is the summary with links:
- [v2,1/3] remoteproc: pru: Fixup interrupt-parent logic for fw events
https://git.kernel.org/andersson/remoteproc/c/6d1f2803cb6b
- [v2,2/3] remoteproc: pru: Fix wrong success return value for fw events
https://git.kernel.org/andersson/remoteproc/c/1fe72bcfac08
- [v2,3/3] remoteproc: pru: Fix and cleanup firmware interrupt mapping logic
https://git.kernel.org/andersson/remoteproc/c/880a66e026fb
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:[~2021-04-14 2:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 15:56 [PATCH v2 0/3] PRU firmware event/interrupt mapping fixes Suman Anna
2021-04-07 15:56 ` [PATCH v2 1/3] remoteproc: pru: Fixup interrupt-parent logic for fw events Suman Anna
2021-04-07 15:56 ` [PATCH v2 2/3] remoteproc: pru: Fix wrong success return value " Suman Anna
2021-04-07 15:56 ` [PATCH v2 3/3] remoteproc: pru: Fix and cleanup firmware interrupt mapping logic Suman Anna
2021-04-07 16:10 ` Mathieu Poirier
2021-04-13 18:10 ` [PATCH v2 0/3] PRU firmware event/interrupt mapping fixes Suman Anna
2021-04-14 2: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=161836681090.7360.10429412919501045588.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=s-anna@ti.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