[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUV3cH5r6gScYt18tpaJx49oXtrn56BMTuj5jJQwvd_zig@mail.gmail.com>
Date: Tue, 9 Jul 2013 11:50:38 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: Tree for Jul 9
On Tue, Jul 9, 2013 at 9:01 AM, Stephen Rothwell <sfr@...b.auug.org.au> 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.
- 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists