From: Pekka Enberg <penberg@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: piotr@hosowicz.com, Jonathan Cameron <jic23@cam.ac.uk>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Build issue with linux next. duplicate member _count in mm_types.h
Date: Thu, 07 Jul 2011 22:51:15 +0300 [thread overview]
Message-ID: <1310068275.21902.63.camel@jaguar> (raw)
In-Reply-To: <alpine.DEB.2.00.1107071413290.24437@router.home>
On Thu, 2011-07-07 at 14:14 -0500, Christoph Lameter wrote:
> On Thu, 7 Jul 2011, Pekka Enberg wrote:
>
> > > I attach it. Your patch seems to had worked, I finish making the package.
> >
> > I'm confused. Does Christoph's patch fix the problem for everyone?
>
> Guess so (heard nothing to the contrary) but I still would like to know
> what caused it. My best guess right now its gccs 4.6s stricter checking.
OK, I applied the patch. Hopefully it will fix build breakage in
linux-next.
next prev parent reply other threads:[~2011-07-07 19:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 9:55 Build issue with linux next. duplicate member _count in mm_types.h Jonathan Cameron
2011-07-06 9:55 ` Jonathan Cameron
2011-07-06 14:46 ` Christoph Lameter
2011-07-07 13:05 ` Piotr Hosowicz
2011-07-07 13:42 ` Christoph Lameter
2011-07-07 13:48 ` Piotr Hosowicz
2011-07-07 14:09 ` Christoph Lameter
2011-07-07 14:41 ` Piotr Hosowicz
2011-07-07 14:54 ` Christoph Lameter
2011-07-07 14:57 ` Jonathan Cameron
2011-07-07 19:07 ` Pekka Enberg
2011-07-07 19:14 ` Christoph Lameter
2011-07-07 19:51 ` Pekka Enberg [this message]
2011-07-07 22:56 ` Steven Newbury
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=1310068275.21902.63.camel@jaguar \
--to=penberg@kernel.org \
--cc=cl@linux.com \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=piotr@hosowicz.com \
--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.