From: Glauber Costa <glommer@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Zheng Liu <wenqing.lz@taobao.com>,
Dave Chinner <dchinner@redhat.com>,
Glauber Costa <glommer@openvz.org>
Subject: Re: linux-next: manual merge of the akpm tree with the ext4 tree
Date: Thu, 20 Jun 2013 01:08:18 +0400 [thread overview]
Message-ID: <20130619210817.GA30417@localhost.localdomain> (raw)
In-Reply-To: <20130619185917.GC24587@thunk.org>
On Wed, Jun 19, 2013 at 02:59:17PM -0400, Theodore Ts'o wrote:
> On Wed, Jun 19, 2013 at 10:06:35AM -0700, Andrew Morton wrote:
> >
> > Merge the ext4 change early, please. The core shrinker changes aren't
> > 100% certain at this time - first they need to stop oopsing ;)
>
> Ack, sounds like a plan.
>
> Are they oopsing often enough that they are likely to interfere with
> running regression tests on linux-next?
>
I have only received one report so far. It will really depend on how likely it
is for other people to hit it - wether or not other people hit it easily is also
good info...
next prev parent reply other threads:[~2013-06-19 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 7:27 linux-next: manual merge of the akpm tree with the ext4 tree Stephen Rothwell
2013-06-19 7:44 ` Glauber Costa
2013-06-19 7:45 ` Stephen Rothwell
2013-06-19 14:20 ` Theodore Ts'o
2013-06-19 17:06 ` Andrew Morton
2013-06-19 18:59 ` Theodore Ts'o
2013-06-19 21:08 ` Glauber Costa [this message]
2013-06-19 7:48 ` Zheng Liu
2013-06-19 7:48 ` Zheng Liu
-- strict thread matches above, loose matches on Subject: below --
2013-08-07 5:19 Stephen Rothwell
2013-08-09 22:21 ` Kees Cook
2013-08-09 22:34 ` Andrew Morton
2013-08-07 5:16 Stephen Rothwell
2013-07-16 4:56 Stephen Rothwell
2013-07-16 4:53 Stephen Rothwell
2012-07-16 6:52 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=20130619210817.GA30417@localhost.localdomain \
--to=glommer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dchinner@redhat.com \
--cc=glommer@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.com \
/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.