From: patchwork-bot+linux-remoteproc@kernel.org
To: Nikita Shubin <nikita.shubin@maquefel.me>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] remoteproc: error on kick missing
Date: Thu, 26 Mar 2020 05:47:00 +0000 [thread overview]
Message-ID: <158520162008.22016.336406441463178075.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200228110804.25822-1-nikita.shubin@maquefel.me>
Hello:
This patch was applied to andersson/remoteproc.git (refs/heads/for-next).
On Fri, 28 Feb 2020 14:08:04 +0300 you wrote:
> From: Nikita Shubin <NShubin@topcon.com>
>
> .kick method not set in rproc_ops will result in:
>
> 8<--- cut here ---
> Unable to handle kernel NULL pointer dereference
>
> [...]
Here is a summary with links:
- remoteproc: error on kick missing
https://git.kernel.org/andersson/remoteproc/c/791c13b709dd51eb37330f2a5837434e90c87c27
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
prev parent reply other threads:[~2020-03-26 5:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 11:08 [PATCH] remoteproc: error on kick missing nikita.shubin
2020-03-02 17:44 ` Mathieu Poirier
2020-03-02 21:43 ` Bjorn Andersson
2020-03-03 15:56 ` Mathieu Poirier
2020-03-04 14:09 ` nikita.shubin
2020-03-04 16:11 ` Mathieu Poirier
2020-03-05 11:02 ` [PATCH v3 0/1] remoteproc: Fix NULL pointer dereference in rproc_virtio_notify Nikita Shubin
2020-03-05 11:02 ` [PATCH v3 1/1] " Nikita Shubin
2020-03-06 7:03 ` [PATCH v4] " Nikita Shubin
2020-03-06 7:24 ` [PATCH v5] " Nikita Shubin
2020-03-09 14:22 ` Arnaud POULIQUEN
2020-03-10 12:08 ` Nikita Shubin
2020-03-10 13:19 ` Arnaud POULIQUEN
2020-03-11 20:01 ` Bjorn Andersson
2020-03-16 16:55 ` Mathieu Poirier
2020-03-17 14:24 ` Arnaud POULIQUEN
2020-03-21 17:57 ` Bjorn Andersson
2020-03-26 5:46 ` patchwork-bot+linux-remoteproc
2020-03-26 5:47 ` 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=158520162008.22016.336406441463178075.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=nikita.shubin@maquefel.me \
/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