Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes: > On Mon, Feb 25, 2019 at 10:43:47AM +0100, LABBE Corentin wrote: >> On Sun, Feb 24, 2019 at 02:54:28PM +0100, gregkh@xxxxxxxxxxxxxxxxxxx wrote: >> > The patch below was submitted to be applied to the 4.20-stable tree. >> > >> > I fail to see how this patch meets the stable kernel rules as found at >> > Documentation/process/stable-kernel-rules.rst. >> > >> > I could be totally wrong, and if so, please respond to >> > <stable@xxxxxxxxxxxxxxx> and let me know why this patch should be >> > applied. Otherwise, it is now dropped from my patch queues, never to be >> > seen again. >> > >> > thanks, >> > >> > greg k-h >> > >> >> Hello >> >> Without this patch, we cannot boot a defconfig on ARC, and this is >> critical for testing ARC devices in kernelCI. > > But this means you have never been able to boot a defconfig on ARC, > right? So this is a new "feature" you are adding :) Correct, we've never been able to boot an *upstream* defconfig in kernelCI for ARC. > If you wait one more week, all is good, you can do this for 5.0, and > when I drop 4.20 in another few weeks, all is fine. > >> Why this patch is not a real stable patch, it is a strong requirement >> for testing all future stable release on kernelCI. > > Only for 4.20. > > And normally kernelci uses a specific configuration for the board it is > testing, not defconfig. Or am I mistaken? We only boot upstream defconfigs, hence the backport request I guess. Without it, we'll survive. It just means we can only boot v5.1+ on ARC in kernelCI. Kevin
