On Tue, Apr 16, 2013 at 10:32 AM, Grant Likely <grant.likely@xxxxxxxxxxxx> wrote: > On Mon, 8 Apr 2013 11:32:26 -0700, Alexandre Courbot <gnurou@xxxxxxxxx> wrote: >> From: Alexandre Courbot <acourbot@xxxxxxxxxx> >> >> Second version, based on -next this time, of the GENERIC_GPIO removal patches. >> Considering there is only a short amount of time before 3.10 merge window opens, >> I hope this version will be considered for inclusion, otherwise we'd end up >> with an half-baked removal or I will have to rebase everything for 3.11. :( >> >> Grant, if this is ok with you, how shall we have this integrated into your >> branch? Half of this has been tested in my -next branch, and the present patches >> make the next half, should I resend you the whole series based on -next and >> withdraw my branch? This is a fast moving target, so we should try and shoot >> that duck as soon as we can! :) > > Most of your patches are already in linux-next in a separate branch, so > the first thing to do is get these remaining patches into that same > branch. As we discussed on IRC, you need to move yor current > "remove_generic_gpio" branch into your for_next branch so that it is > picked up by Stephen. There isn't any functional change there, but it > means that your series will be based on a defined point of Linus' tree > (v3.9-rc6) instead of an arbitrary commit point between -rc3 and -rc4. On second thought, no don't do this. Just leave it as is. It is more important to retain the test coverage you've already had in linux-next on these commits. Just apply the patches I've acked onto your existing for_next branch. g. -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
