From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 9
Date: Tue, 9 Jul 2013 11:50:38 +0200 [thread overview]
Message-ID: <CA+icZUV3cH5r6gScYt18tpaJx49oXtrn56BMTuj5jJQwvd_zig@mail.gmail.com> (raw)
In-Reply-To: <20130709170155.a212513b3a95d78e404e70db@canb.auug.org.au>
On Tue, Jul 9, 2013 at 9:01 AM, Stephen Rothwell <sfr@canb.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
next prev parent reply other threads:[~2013-07-09 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 7:01 linux-next: Tree for Jul 9 Stephen Rothwell
2013-07-09 9:50 ` Sedat Dilek [this message]
2013-07-09 9:54 ` Sedat Dilek
2014-07-09 8:31 Stephen Rothwell
2015-07-09 4:09 Stephen Rothwell
2018-07-09 6:35 Stephen Rothwell
2019-07-09 12:00 Stephen Rothwell
2020-07-09 9:18 Stephen Rothwell
2020-07-09 10:11 ` Anders Roxell
2021-07-09 3:24 Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+icZUV3cH5r6gScYt18tpaJx49oXtrn56BMTuj5jJQwvd_zig@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).