Hi Leo,
Leo Famulari writes:
> What commit do these patches apply to? They don't apply for me on the
> current master branch.
I created a v4 containing the v6.6.1 update as well as fixed the
patches so they'll apply on the kernel-updates branch with the commits
out of the recent updates [0] in
On Mon, Nov 06, 2023 at 11:41:47PM +0100, Wilko Meyer wrote:
> Agreed, thanks for mentioning this! I'll send a v3 of this patch series
> that splits up the changes in two commits; one introducing 6.6, the
> other making it the default kernel (which can be applied after a couple
> of days if 6.6
Hi Leo,
Leo Famulari writes:
> I think it's helpful to wait a couple days before doing that after
> adding the new kernel series. This gives people a chance to test things
> to before we deploy the update for all users.
Agreed, thanks for mentioning this! I'll send a v3 of this patch series
On Wed, Nov 01, 2023 at 03:32:27PM +0100, Wilko Meyer wrote:
> * gnu/packages/linux.scm (linux-libre-6.6-version,
> linux-libre-6.6-gnu-revision,
> deblob-scripts-6.6, linux-libre-6.6-pristine-source, linux-libre-6.5-source,
> linux-libre-headers-6.6, linux-libre-6.6): New variables.
> *
On Wed, Nov 01, 2023 at 03:32:27PM +0100, Wilko Meyer wrote:
> * gnu/packages/linux.scm (linux-libre-6.6-version,
> linux-libre-6.6-gnu-revision,
> deblob-scripts-6.6, linux-libre-6.6-pristine-source, linux-libre-6.5-source,
> linux-libre-headers-6.6, linux-libre-6.6): New variables.
> *
