From: Sedat Dilek <sedat.dilek@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 4
Date: Thu, 4 Jul 2013 09:41:14 +0200 [thread overview]
Message-ID: <CA+icZUXchb2H=ZZ0Zv+vA43x0CNVSbLvPptawnBR+OUpOzqP6A@mail.gmail.com> (raw)
In-Reply-To: <20130704160652.4f76f0ee43877a6e726d6c8b@canb.auug.org.au>
On Thu, Jul 4, 2013 at 8:06 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Changes since 20130703:
>
> The net-next tree lost its build failure.
>
> The akpm tree gained a conflict against the kbuild tree and lost lots of
> patches that turned up elsewhere.
>
> ----------------------------------------------------------------------------
>
Just FYI:
People building with "CONFIG_MEMCG_KMEM=n" (still) need an extra patch
pending in mmots-tree [1].
( Unfortunately, it does not cleanly apply against next-20130704. )
- Sedat -
[1] http://ozlabs.org/~akpm/mmots/broken-out/memcg-use-css_get-put-when-charging-uncharging-kmem-fix-fix.patch
next prev parent reply other threads:[~2013-07-04 7:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 6:06 linux-next: Tree for Jul 4 Stephen Rothwell
2013-07-04 6:06 ` Stephen Rothwell
2013-07-04 7:41 ` Sedat Dilek [this message]
2013-07-04 8:21 ` Sedat Dilek
2013-07-04 8:40 ` Sedat Dilek
2013-07-04 8:45 ` Andrew Morton
2013-07-04 9:12 ` Sedat Dilek
2014-07-04 6:42 Stephen Rothwell
2014-07-04 8:42 ` Sachin Kamat
2014-07-04 15:10 ` Stephen Rothwell
2014-07-05 0:48 ` J. Bruce Fields
2014-07-05 14:57 ` Sachin Kamat
2014-07-06 4:54 ` Nick Krause
2014-07-06 5:17 ` Nick Krause
2014-07-06 5:21 ` Nick Krause
2014-07-06 5:34 ` Nick Krause
2014-07-06 5:42 ` Nick Krause
2014-07-05 14:56 ` Sachin Kamat
2016-07-04 8:43 Stephen Rothwell
2017-07-04 5:44 Stephen Rothwell
2018-07-04 5:57 Stephen Rothwell
2019-07-04 12:09 Stephen Rothwell
2019-07-04 12:24 ` Stephen Rothwell
2019-07-04 12:40 ` Greg Kroah-Hartman
2019-07-06 8:34 ` Greg Kroah-Hartman
2019-07-06 9:44 ` Stephen Rothwell
2019-07-06 9:46 ` Greg Kroah-Hartman
2019-07-06 10:17 ` Stephen Rothwell
2019-07-06 14:33 ` Greg Kroah-Hartman
2019-07-06 15:42 ` Greg Kroah-Hartman
2022-07-04 8:21 Stephen Rothwell
2023-07-04 3:43 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+icZUXchb2H=ZZ0Zv+vA43x0CNVSbLvPptawnBR+OUpOzqP6A@mail.gmail.com' \
--to=sedat.dilek@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.