Re: About CIP kernel maintenance policy for new hardware support backporting
Thanks for pointed out.Agree.
We think that we need to add the following sentences.
We do not apply patches that have not been applied to upstream
If you want to add new features or hardware, they need to be applied into upstream.
Also, you may not be able to easily apply the patches on Upstream. In such a case,
you need to describe in the commit message of patch what modifications have been made
from the original patch.
In addition to these, we may need to describe the supported hardware (CPU, boards) and
test environment as well.
From: Yoshitake Kobayashi [mailto:yoshitake.kobayashi@...]
Sent: Wednesday, July 10, 2019 9:56 PM
Cc: cip-dev@...; pavel@...; iwamatsu nobuhiro(岩松 信洋 ○ＳＷＣ□ＯＳＴ) <nobuhiro1.iwamatsu@...>
Subject: Re: [cip-dev] About CIP kernel maintenance policy for new hardware support backporting
Thanks for pointed out.
You can find the following sentence on the page.
an SLTS branch may include larger changes to support new hardware, to bridge the gap between SLTS branches.I think we need to write much clear to mention what kind of patches we can accept to CIP SLTS tree and how to approve(?) it by CIP.
2019年7月10日(水) 15:42 <hiraku.toyooka@...>:
I have a question about CIP kernel maintenance policy.
Can CIP kernel accept backport patches for new hardware support (not
I read the following document and it seems to describe only acceptable fixes.
On the other hand, Current linux-4.19.y-cip branch accepts some hardware
support patches such as RZ/G2E(r8a774c0) from upstream.
So I wonder if some policy about new hardware support exists.
Cybertrust Japan Co., Ltd.
cip-dev mailing list