New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Missing policy to upstream Linux patches #166

Open

paulmenzel opened this issue Nov 3, 2020 · 0 comments

Contributor

paulmenzel commented Nov 3, 2020 •

edited

Loading

Currently, there does not seem to be a policy to upstream the Linux patches, adding maintenance burden.

Forward porting these patches takes a lot of effort, which – once upstream – the Linux community would take care of.
Work with other network operating systems, like Open Network Linux, which also has no upstreaming policy, is duplicated.
The original patch authors are often gone after a while.

OpenBMC has a Development Process, I recommend to adapt.

Upstream is key

In order to leverage the benefits of using the Linux kernel, OpenBMC maintains a policy that all kernel code will be merged upstream.

However, there are often cases where product requirements mean that synchronising with an upstream schedule is not always possible. This process aims to allow both goals (upstream inclusion and a useful OpenBMC build) to occur in parallel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment