Issues with 5.14 and 5.14.1 releases:
- apcusd produces usb full queue messages
- reboot loop on atom CPU (dedibox)

Rollback to 5.13

- Linux 5.14

- Linux 5.13.0

- Upgrade to linux-5.12.0-seblu
- Add kernel-install-hook as dep

- Release 5.11

- Update to 5.10.13
- Add 5.10.8

- Remove 5.10.0. Breaks RAID arrays...
- Add 5.10.1

- New 5.10.0 kernel

- New kernel 5.9.5
- New kernel 5.8.18
- Remove kernels with bluetooth vuln

- Update to 5.9.1 (security)

- Release 5.9.0

- Release of linux 5.8.0

New upstream kernel release: 5.7.2

New upstream kernel release: 5.7

Bump to 5.6.3

New kernel 5.6 release

- Linux 5.5.0
- Linux 4.19.99
- Linux 4.9.211

- Linux 5.4.0

- linux-5.3.0-seblu
- linux-4.19.73-seblu
- linux-4.9.193-seblu

- linux-4.19.60-seblu
- linux-4.9.186-seblu

Add Linux 5.2.0-1

- Linux 4.19.53-1

- Bump to 4.9.182

- Up to 5.1.5 because of bug on fstrim

- Linux 5.1.2
- Linux 4.19.43
- Linux 4.9.176

- Upgrade to linux 5.0.0

- rename 4.9 and 4.19 packages
- bump to 4.19.26

- linux-4.19.20-seblu
- linux-4.9.155-seblu

- Add linux-seblu-4.19-meta
- Add provides=('linux-seblu-meta') for old version

For free :)

- linux-4.19.16-seblu
- linux-4.9.151-seblu

Move back to 4.19.x because of perf issues with 4.20

- linux-4.20.2-seblu
- linux-4.9.150-seblu

No more conflict between split packages. Both are allowed on the same system.

- Introduce linux-seblu-4.9-meta to track 4.9 releases
- Add kernel 4.20

linux-4.18.20-seblu
linux-4.9.146-seblu