On 09/06/2012 07:36 PM, Stephen Warren wrote: > On 09/06/2012 07:00 PM, Mark Brown wrote: >> On Thu, Sep 06, 2012 at 05:47:33PM -0600, Stephen Warren wrote: >> >>> Mark, I'd like to take this patch through the Tegra tree, since it's a >>> dependency for the series that converts Tegra to dmaengine. Thanks. >> >> Since it's a fix I was going to send it as a patch for 3.6 so that >> shouldn't be an issue? > > Oh right, that makes sense too, thanks. Mark, This patch shows up in your ASoC for-next branch, but not in your for-3.6 or for-3.7 branches. I think gitk is telling me that you simply forgot to push your latest for-3.6 branch to kernel.org when you pushed your updated for-next. Anyway, since this patch didn't make 3.6-rc5, it is difficult for me to use as a baseline for any branches destined for 3.7, since I'm supposed to send my pull requests to arm-soc before 3.6-rc6 is released, yet if this patch goes into 3.6, it won't be there until 3.6-rc6 at the earliest. I'm not sure how best to resolve this; is it possible for me to take the patch through the Tegra tree instead, as I originally intended? -- 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
