OpenBMC Kernel Development Process

[Andrew Jeffery]

On Thu, 2017-02-02 at 15:44 +1030, Joel Stanley wrote:
> # Processes
> 
> ## Patch submitters (wishing to have a change included through this process)
> 
>  - ensure that patches conform to base-level quality guidelines
>    - no warnings from checkpatch
>    - does not introduce errors or warnings, for specific defconfigs
>       - aspeed_g4_defconfig
>       - aspeed_g5_defconfig
>    - boot test the kernel using the qemu simulation environment
>       - At a minimum, the system should boot to a userspace prompt of
> the OpenBMC userspace
>  - submit upstream first
>  - submit proposed patches to openbmc at lists.ozlabs.org
>     - This version of hte patch should contain "[PATCH linux
> <branch>]" in the subject, where <branch> is the name of the current
> OpenBMC development tree

It should be noted that if you're cherry-picking changes applied
upstream to backport them to OpenBMC you should be wary of `git send-
email` Cc'ing people, e.g upstream maintainers, who have Signed-off-by
tags on the cherry-picked patch.

To avoid this you can do: `git send-email --suppress-cc=sob`.

Separately it would pay to do a `git send-email --dry-run` beforehand,
and check the result.

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170203/fa0d5e83/attachment.sig>