sitonapanotis wrote:graysky wrote:You could build it from ABS applying the upstream patch in the prepare function; if the patch is already applied, makepkg will exit with an error and you'll know without trying it.I tried applying a patch someone provided on the bug report to the normal 3.12 kernel with ABS but it quit with an error in prepare.
From what I understand, I can easily upgrade my kernel by applying patches to it, opposed to recompiling the kernel every time. I'm trying to go from kernel 3.2.51 to 3.2.54 by applying all the patches in between.
I'm trying to patch my 3.2.51 kernel (I downloaded it from www.kernel.org and compiled it myself) to 3.2.52.
With kernel 3.4.3 acpi video doesnt exist.This problem is fixed by this bug ;https://bugzilla.kernel.org/show_bug.cgi?id=43168Please add this patch to chakra kernel or update kernel to 3.4.5 because kernel is come with this patch. İ dont change my laptop brightness, thanks.
I've recently applied a one-line patch to drivers/bluetooth/btusb.c in order to enable compatibility with my Bluetooth device. However, whenever I get a kernel upgrade, the patch will be lost until someone backports it (which isn't likely). Is there a way for me to run a script and patch each new kernel upgrade automatically?
Details on how to apply the patch can be found here on Ask Ubuntu.
For each Linux kernel version, there is a patch file available for download. For instance, linux-3.12.22 has a corresponding patch-3.12.22.
What is the purpose of that patch? To always patch the corresponding kernel before compiling it, or to bring a former kernel version up-to-date with the kernel that the patch matches (3.12.22, in this case)?
I'm using linux-lqx from AUR and I'm patching it with reiser4 support. I'm after some updates and never had any problem, I was just adding patch -p1 -i /path/to/patch after Liquorix' patchset and it was fine. It's still 3.12.x kernel so patch should be valid.