You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because the goal is to demo what it looks like to register multiple chardevs on the same major number. We're being lazy and just using the same file type.
yes it would help because the intention is not explicitly clear.
Thank you for clarifying. It makes sense.
On Friday, March 19, 2021, 5:11:51 p.m. EDT, Alex Gaynor ***@***.***> wrote:
Because the goal is to demo what it looks like to register multiple chardevs on the same major number. We're being lazy and just using the same file type.
Would a comment explaining this help?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Activity
alex commentedon Mar 19, 2021
Because the goal is to demo what it looks like to register multiple chardevs on the same major number. We're being lazy and just using the same file type.
Would a comment explaining this help?
fixes #127 -- added a comment to clarify an example
Merge pull request #128 from Rust-for-Linux/alex-patch-1
omac777 commentedon Mar 23, 2021
bpf: Fix tail_call_reachable rejection for interpreter when jit failed
init: don't panic if mount_nodev_root failed
LoongArch: BPF: Support 64-bit pointers to kfuncs