Vagrant Cascadian <vagrant@debian.org> writes:

> On 2020-03-30, Vagrant Cascadian wrote:
>> And the second patch, switching to 5.5...
>
> And a third, rougher, less well tested patch switching to 5.6... which
> could obviously be squashed into the previous patches and maybe skip 5.5
> altogether.

5.5 is not an LTS kernel, so going straight to 5.6 sounds like the
right thing to do.  However...

> diff --git a/gnu/packages/aux-files/linux-libre/5.5-arm.conf b/gnu/packages/aux-files/linux-libre/5.6-arm.conf
> similarity index 100%
> rename from gnu/packages/aux-files/linux-libre/5.5-arm.conf
> rename to gnu/packages/aux-files/linux-libre/5.6-arm.conf
> diff --git a/gnu/packages/aux-files/linux-libre/5.5-arm64.conf b/gnu/packages/aux-files/linux-libre/5.6-arm64.conf
> similarity index 100%
> rename from gnu/packages/aux-files/linux-libre/5.5-arm64.conf
> rename to gnu/packages/aux-files/linux-libre/5.6-arm64.conf
> diff --git a/gnu/packages/aux-files/linux-libre/5.5-i686.conf b/gnu/packages/aux-files/linux-libre/5.6-i686.conf
> similarity index 100%
> rename from gnu/packages/aux-files/linux-libre/5.5-i686.conf
> rename to gnu/packages/aux-files/linux-libre/5.6-i686.conf
> diff --git a/gnu/packages/aux-files/linux-libre/5.5-x86_64.conf b/gnu/packages/aux-files/linux-libre/5.6-x86_64.conf
> similarity index 100%
> rename from gnu/packages/aux-files/linux-libre/5.5-x86_64.conf
> rename to gnu/packages/aux-files/linux-libre/5.6-x86_64.conf

This does not seem right.  Surely there are _some_ configuration changes
in 5.6?