> This patch bumps the 4.4 kernel from .28 to .30 and refreshes the patches.
A question regarding the 'patch refreshing' and my previous patch for 4.4.29. I want to figure out where my workflow is erroneous, or what things I did not understand when refreshing a patch series during a kernel upgrade like this. For example let me take the first refreshing you submitted (besides 4.4.28->30 in kernel-version.mk): The file 'target/linux/bcm53xx/patches-4.4/405-mtd-spi-nor-detect-JEDEC-incompatible-w25q128-using-.patch' patches the kernel driver 'drivers/mtd/spi-nor/spi-nor.c' Now with your patch refreshing, you adjust the offsets in spi-nor.c However, this file (spi-nor.c) was last changed back in July (2016-07-14). So why is it required to refresh this patch on 4.4.28 -> .30, when this file was last changed during 4.4.15 -> .16 ? Don't get me wrong, I just want to understand where I have to adjust my workflow. Best regards, P. Wassi _______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
