[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120516175322.GA3094@kroah.com>
Date: Wed, 16 May 2012 10:53:22 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Shuah Khan <shuahkhan@...il.com>
Cc: devel@...verdev.osuosl.org, linaro-kernel@...ts.linaro.org,
Kees Cook <keescook@...omium.org>,
Arnd Bergmann <arnd@...db.de>, patches@...aro.org,
Marco Stornelli <marco.stornelli@...il.com>,
Stephen Boyd <sboyd@...eaurora.org>,
linux-kernel@...r.kernel.org,
Anton Vorontsov <anton.vorontsov@...aro.org>, arve@...roid.com,
Jesper Juhl <jj@...osbits.net>,
John Stultz <john.stultz@...aro.org>,
Colin Cross <ccross@...roid.com>,
Rebecca Schultz Zavin <rebecca@...roid.com>,
WANG Cong <xiyou.wangcong@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
kernel-team@...roid.com, Thomas Meyer <thomas@...3r.de>
Subject: Re: [PATCH 4/6] staging: android: persistent_ram: Move to
fs/pstore/ram_core.c
On Wed, May 16, 2012 at 10:29:46AM -0600, Shuah Khan wrote:
> On Wed, 2012-05-16 at 08:05 -0700, Greg Kroah-Hartman wrote:
>
> >
> > After applying this patch, and building things, I get the following
> > errors:
>
> Greg,
>
> > What went wrong?
> >
> > I've now applied the first 3 patches in this series to my tree, plus the
> > 2 others from the linux-next tree, so care to just fix up these last
> > three and resend them?
>
> Picking [PATCH 5/6] staging/android: Remove ram_console driver should
> fix this problem. This patches removes ram_console.c from the staging
> area.
That's nice, but you CAN NOT BREAK THE BUILD at any step of a patch
series progress.
So please rework this to prevent this from happening, as it is, I can
not accept these.
greg k-h
--
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