On Tue, Mar 19, 2013 at 11:19:05PM +0900, Masami Hiramatsu wrote: > Hi Jason, > > (2013/03/19 22:33), Jason Cooper wrote: > > On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote: > >> Hi, > >> > >> Here I've hit a bug on the recent kernel. As far as I know, this bug > >> exists on 3.9-rc1 too. > >> > >> When I tried the latest mvebu for-next tree > >> (git://git.infradead.org/users/jcooper/linux.git mvebu/for-next), > > > > FYI: that branch isn't stable, it's used as a merge-test of > > arm-soc/for-next (also not stable) and any branches I am trying to push > > upstream that day. > > Thanks! could you tell me which branch is stable? > (however, I'd like to try new fixes/features on my device too :))
Generally, we advise using one of Linus' tags (eg v3.9-rc3). Only if that doesn't work, seek out a branch containing the fix/feature. When in doubt, I'll do: $ ./scripts/get_maintainer.pl -f drivers/net/ethernet/marvell/mvneta.c and ask those listed which branch might contain a fix or feature. In this case, it'll probably go through David Miller and the netdev mailinglist, but it isn't there yet. ;-) hth, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
