cip-kernel-config usage

cip-kernel-config usage

[Chris Paterson]

Hello kernel team, all,

The cip-kernel-config[0] repo holds the various kernel configurations which CIP uses to maintain the Linux kernel.

In addition to .config/defconfig files, we also have various .sources files, which get generated by the Makefile included in the repository.
My original understanding (backed up by the README[1]) is that these .sources files contain a list of all the kernel source files used by a particular config(branch/arch/config-name.sources), or for all configs (branch/all.sources).
These files would then be used to help direct the efforts of the kernel team when maintaining the kernel.
Is this still the case? Or has this practice been stopped?

Also, there seems to be some kind of "warnings" configuration[2] which is used to define kernel configurations that are not recommended to be used.
However, we only have this in place for 4.4.y-cip[3].
Do we intend to ever revisit using this system for the newer kernel versions? 


[0] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config
[1] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/README.md
[2] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/README.md#warnings
[3] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/-/blob/master/4.4.y-cip/warnings.yml

Kind regards, Chris

Re: [cip-dev] cip-kernel-config usage

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

Hi!

> The cip-kernel-config[0] repo holds the various kernel configurations which CIP uses to maintain the Linux kernel.
> 
> In addition to .config/defconfig files, we also have various .sources files, which get generated by the Makefile included in the repository.
> My original understanding (backed up by the README[1]) is that these .sources files contain a list of all the kernel source files used by a particular config(branch/arch/config-name.sources), or for all configs (branch/all.sources).
> These files would then be used to help direct the efforts of the kernel team when maintaining the kernel.
> Is this still the case? Or has this practice been stopped?

That is still the
case. git@gitlab.com:cip-project/cip-kernel/lts-commit-list.git , our
review scripts (commit.py and relevant.py) mark those commits that
affect files actually used our build.

We should eventually use the files for 6.1 reviews; I don't think we
need them for for branches we are not maintinaing (like 5.4).

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]