On 08/18/10 15:15, Brice Goglin wrote:
This patch (actually 01ab17887 in 2.6.36-rc1) reveals what looks like a problem to me: make kernelrelease always regenerates include/config/kernel.release even if it's already more recent than include/config/auto.conf. Is this the expected behavior? Do we really need include/config/kernel.release to depend on FORCE?
I think so, because "LOCALVERSION=" can be given from command line, so we need to regenerate it. Or am I missing your point here? -- The opposite of love is not hate, it's indifference. - Elie Wiesel -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
