[Letux-kernel] New LetuxOS kernel trees for Replicant

Andreas Kemnade andreas at kemnade.info
Sat Jun 29 22:40:47 CEST 2019


On Sat, 29 Jun 2019 22:23:38 +0200
"H. Nikolaus Schaller" <hns at goldelico.com> wrote:

> > Am 29.06.2019 um 22:02 schrieb Andreas Kemnade <andreas at kemnade.info>:
> > 
> > On Sat, 29 Jun 2019 21:53:54 +0200
> > "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
> >   
> >> Hi,
> >> I have updated the replicant variants of our source tree
> >> 
> >> 4.10.5 -> 4.14.129			http://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/letux-4.14.129-replicant
> >> work/josua/android-4.17 -> 4.19.56	http://git.goldelico.com/?p=letux-kernel.git;a=shortlog;h=refs/heads/letux-4.19.56-replicant
> >> 
> >> There were only minor merge conflicts, mostly in Kconfig and Makefile.
> >> Only the two patches for the lowmemorykiller did not apply on 4.19.56, so they are missing:
> >> 
> >> http://git.goldelico.com/?p=letux-kernel.git;a=commit;h=fbc6ce18694bf8c255525327674598e5ed3b9ced
> >> http://git.goldelico.com/?p=letux-kernel.git;a=commit;h=6c77d5cea4464c40dcfa382e096252c3cafae1b7
> >> 
> >> I have not been able to really test these kernels but we should continue fixing them because those are now long-term kernels.
> >> 
> >> So we should update the manifest files to point to these branches.
> >> 
> >> What I am not exactly sure about is if we should include the full version number in the branch name, i.e. "letux-4.19.56-replicant" which
> >> means we will create newer and newer branches with different names over the time and have to make the manifest track that. This more or less treats git branches like git tags (and is not more resource hungry).
> >> 
> >> Or if we should have a single branch "letux-4.19-replicant" where we merge in future branches.  
> > 
> > This with CONFIG_LOCALVERSION_AUTO=y,
> > then we know which kernel we are using.  
> 
> Well, the uImage can always queried by "file" and the running system by "uname".
> 
well, you do not get the git commit used.

> I think this CONFIG adds the -gxxxxxxxx things which gives a different version even if
> you have local unpublished patches...
>
well, that is a nice feature. 

> So I thing that will break the LetuxOS kernel build system.
> 
At least I am using it for bisect things, so I can check what
I am really running.

Regards,
Andreas


More information about the Letux-kernel mailing list