From: patchwork-bot+linux-remoteproc@kernel.org
To: Siddharth Gupta <sidgup@codeaurora.org>
Cc: linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH] remoteproc: core: Move cdev add before device add
Date: Wed, 23 Jun 2021 21:50:05 +0000 [thread overview]
Message-ID: <162448500570.18278.8235199339523096069.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1618946805-26970-1-git-send-email-sidgup@codeaurora.org>
Hello:
This patch was applied to andersson/remoteproc.git (refs/heads/for-next):
On Tue, 20 Apr 2021 12:26:45 -0700 you wrote:
> When cdev_add is called after device_add has been called there is no
> way for the userspace to know about the addition of a cdev as cdev_add
> itself doesn't trigger a uevent notification, or for the kernel to
> know about the change to devt. This results in two problems:
> - mknod is never called for the cdev and hence no cdev appears on
> devtmpfs.
> - sysfs links to the new cdev are not established.
>
> [...]
Here is the summary with links:
- remoteproc: core: Move cdev add before device add
https://git.kernel.org/andersson/remoteproc/c/c6659ee893e2
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-06-23 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 19:26 [PATCH] remoteproc: core: Move cdev add before device add Siddharth Gupta
2021-04-22 18:04 ` Mathieu Poirier
2021-04-23 2:12 ` Siddharth Gupta
2021-04-23 3:01 ` Bjorn Andersson
2021-04-23 21:48 ` Siddharth Gupta
2021-06-23 21:50 ` 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=162448500570.18278.8235199339523096069.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-remoteproc@kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=sidgup@codeaurora.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