On Tue, Jul 9, 2013 at 11:50 AM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > On Tue, Jul 9, 2013 at 9:01 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote: >> Hi all, >> >> Changes since 20130708: >> >> The v4l-dvb tree lost its build failure. >> >> The tip tree gained a conflict against Linus' tree. >> >> The akpm tree lost a patch that turned up elsewhere. >> >> The cpuinit tree lost some patches that turned up in Linus' tree. >> >> ---------------------------------------------------------------------------- >> > > Hi, > > I got today several emails from Andrew, that some post-fixes to > existing patches in mmotm got merged. > Looking into mmotm patch-series, it was not updated since 03-Jul-2013. > > From where is [1]? > It has "memcg: fix build error if CONFIG_MEMCG_KMEM=n" folded in. > Isn't the procedure to get all these patches from Andrew's mmotm? > BTW, the new patch has no furher informations or a vX history and my > credits are gone, too. > Hmmm, another patch where I was involved... Original: "ipc,msg: shorten critical region in msgrcv" Post-Fix: "ipc,msq: fix race in msgrcv(2)" ...strange, not folded in. - Sedat - [1] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=188ba7fb13646c4a4de00a315fbddc2f4cba1d20 [2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=74bd175d0d237894c14adcf0479dd9f22b30c77b > - Sedat - > > > [0] http://ozlabs.org/~akpm/mmotm/broken-out/ > [1] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/mm/memcontrol.c?id=958f4381fa3cb7abd6f63103c9099e648595a27e -- 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
