On Mon, Mar 5, 2012 at 6:57 PM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: > Hi Paul, > > I noticed this merge in the moduleh tree: > > dc69707e944e "Merge branch 'module-3.4' into for-sfr" > > This merge result in multplie includes of kernel.h in lib/average.c and > lib/list_debug.c. Is there a better way to present these into linux-next vs. me merging them into one stream? I want to keep the module-3.4 content separate from the bug-3.4 content (and let Linus do the pull & merge) but at the same time I want these commit IDs tested in linux-next. The topics are most likely one-shot deals, so adding a separate entity into linux-next for each of them doesn't seem to be worthwhile. Anyway for now, I'll go re-check the merge and make sure it is dup free for tomorrow. Thanks for the heads up. Paul. -- > > -- > Cheers, > Stephen Rothwell sfr@xxxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
