Mark Brown wrote: > > On Thu, Dec 02, 2010 at 08:01:36AM -0800, Stephen Warren wrote: > > > Could you please cherry-pick the changes listed below; they fix some issues > > in the voltage regulator driver used by Seaboard which were fixed in the > > ChromeOS project, and just recently upstreamed. > > Please don't cherry pick changes over into a branch which is destined > for mainline - the patches will appear in mainline in the next merge > window and should go a single time via the expected tree. If they're > urgently needed in the Tegra tree they should probably be dropped from > the regulator tree, or a branch of the regulator tree merged into the > Tegra tree. Sorry, I thought git would make this magically work, and just drop the identical change when pushing changes from linux-tegra-2.6.36. Equally, I was under the impression that patches should initially be sent Where MAINTAINERS indicates, then pulled back to lower trees as needed. Finally, I though linux-tegra-2.6.36 wasn't itself destined for upstream directly; instead, isn't the for-next or tegra/for-next the branch destined for upstream? Thanks for the help. -- nvpublic -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
