From: Jonathan Cameron <jic23@cam.ac.uk>
To: piotr@hosowicz.com
Cc: Christoph Lameter <cl@linux.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@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 15:57:17 +0100 [thread overview]
Message-ID: <4E15C94D.9080205@cam.ac.uk> (raw)
In-Reply-To: <4E15C59E.5000900@example.com>
On 07/07/11 15:41, Piotr Hosowicz wrote:
> On 07.07.2011 16:09, Christoph Lameter wrote:
>> On Thu, 7 Jul 2011, Piotr Hosowicz wrote:
>>
>>> I attach it. Your patch seems to had worked, I finish making the package.
>>
>> I do not see anything remarkable in the config file.
>>
>> Which compiler version are you using?
>>
>> Mine is:
>>
>> christoph@oldy:~$ gcc --version
>> gcc (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5
>> Copyright (C) 2010 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions. There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>> PURPOSE.
>
> Mine is:
>
> aapi205:~# gcc --version
> gcc (Debian 4.6.0-10) 4.6.1 20110526 (prerelease)
> Copyright (C) 2011 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
Mine,
gcc version 4.6.1 20110617 (prerelease) (GCC)
next prev parent reply other threads:[~2011-07-07 14:57 UTC|newest]
Thread overview: 13+ 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 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 [this message]
2011-07-07 19:07 ` Pekka Enberg
2011-07-07 19:14 ` Christoph Lameter
2011-07-07 19:51 ` Pekka Enberg
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=4E15C94D.9080205@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=penberg@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 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).