Messages in this thread | | | From | Linus Torvalds <> | Date | Tue, 1 Nov 2011 16:59:53 -0700 | Subject | Re: [GIT PULL] introduce export.h; reduce module.h usage |
| |
On Mon, Oct 31, 2011 at 5:45 PM, Paul Gortmaker <paul.gortmaker@windriver.com> wrote: > > Please pull the below to get the module.h split content. It has been > tested on v3.1-rc6, soaked in linux-next, and re-tested again lots more > today after rebasing it to allow most of the linux-next finds to be > blended in, where they could not be on the original v3.1-rc6 baseline.
Does it bisect cleanly?
Quite frankly, for something fairly trivial like this where the upside is mainly "slightly faster compile" (and hey, perhaps cleaner source tree), the downsides needs to be minimized. And just looking at the shortlog makes me go: this will be a bisection disaster - people will look for bugs, bisect will go into this series, and things won't compile.
But maybe it's ordered so that the actual module.h split comes last, exactly so that it would be safe and bisectable? I just don't know, and I'd like to know before I pull..
Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |