submit v4l2loopback to the upstream kernel
It would be so much easier if this module were upstream. I searched lkml archives and found no trace of anyone trying to submit it. Is there a reason for that? Are there outstanding problems that need to be fixed first? Can I help?
Posted by jiribohac on Mar 26, 2020, 11:16 AM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
github (Other)0 comments
Proposal to Reorganize the Moderation Team and Review Moderation Policies
github (Other)0 comments
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
github (Other)0 comments
proposal: container/...: generic collection types
github (Other)0 comments
Better Custom Endpoint BYOK
github (Other)0 comments
A concrete policy for backward compatibility until Godot 5.0
github (Other)0 comments
New MTP models not supported
github (Other)0 comments
Tracking: 429 / Capacity Issues
github (Other)0 comments
submit v4l2loopback to the upstream kernel
jiribohacMar 26, 2020, 11:16 AM
It would be so much easier if this module were upstream. I searched lkml archives and found no trace of anyone trying to submit it. Is there a reason for that? Are there outstanding problems that need to be fixed first? Can I help?
Comments (0)
No comments yet. Start the discussion.