Thanks for the email on this, sorry for the delay in responding. I've been traveling for internal meetings for the last week, and won't be back until Feb 8th.

Yes, your understanding is correct, but there's no way to use make menuconfig within the rpm build structure in order to update the configs. You would need to do something on the order of a 'make oldconfig' to use the existing config from the package, then make your changes, save the config, and see what differences are there between the old kernel-alt-4.11.0-aarch64.config and yours, and append the changes to kernel-alt-4.11-0.aarch64.config.

The easiest way to apply and build test kernels is via the mock build utility to build rpms.

On 01/24/2018 03:04 PM, Marcin Wojtas wrote:

Hi Jim,

ACPI support for the Marvell Armada 7k/8k NIC finally landed in the mainline kernel. I backported all required stuff from the upstream to v4.11 and I'm about to create patch that adds a support in the kernel.

Please check if my understanding of adding the patch is sufficient:

1. Place squashed patch in SOURCES/
2. Update SPECS/kernel-alt.spec with the added patch ("5a27f64 - adds

thunderx support patch per cavium list request" is a good reference for that) 3. Update: SOURCES/kernel-alt-4.11.0-aarch64-debug.config SOURCES/kernel-alt-4.11.0-aarch64.config And here's where I have problems. I took kernel-alt-4.11.0-aarch64.config to my v4.11 branch and tried to first build kernel directly from that point - it cannot be done flawlessly, as one have to manually choose multiple kernel CONFIGs resolution.

Further I wanted to use make menuconfig enabled CONFIG_ARCH_MVEBU=y and CONFIG_MVPP2=m.

It would be great, if you were able to let know, what's the easiest and quickest way to apply and test new patches on top of sig-altarch7-aarch64 branch.

Thanks, Marcin