From: Artem Bityutskiy <dedekind1@gmail.com>
To: Will Deacon <will.deacon@arm.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Bastian Hecht <hechtb@googlemail.com>
Subject: Re: Possible regression in arm/io.h
Date: Thu, 25 Oct 2012 09:55:22 +0300 [thread overview]
Message-ID: <1351148122.2507.63.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20121024105223.GC23775@mudshark.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 414 bytes --]
On Wed, 2012-10-24 at 11:52 +0100, Will Deacon wrote:
> (a) Understand what has changed in GCC to cause this error to start
> cropping up.
This is about already quite old gcc 4.6.3, which I use for about 4 last
kernel releases already. So it is only the kernel that changed.
You can download the GCC I used from here:
http://kernel.org/pub/tools/crosstool/
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible regression in arm/io.h
Date: Thu, 25 Oct 2012 09:55:22 +0300 [thread overview]
Message-ID: <1351148122.2507.63.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20121024105223.GC23775@mudshark.cambridge.arm.com>
On Wed, 2012-10-24 at 11:52 +0100, Will Deacon wrote:
> (a) Understand what has changed in GCC to cause this error to start
> cropping up.
This is about already quite old gcc 4.6.3, which I use for about 4 last
kernel releases already. So it is only the kernel that changed.
You can download the GCC I used from here:
http://kernel.org/pub/tools/crosstool/
--
Best Regards,
Artem Bityutskiy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121025/15484097/attachment.sig>
next prev parent reply other threads:[~2012-10-25 6:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 10:38 Possible regression in arm/io.h Bastian Hecht
2012-10-24 10:38 ` Bastian Hecht
2012-10-24 10:52 ` Will Deacon
2012-10-24 10:52 ` Will Deacon
2012-10-24 12:34 ` Bastian Hecht
2012-10-24 12:34 ` Bastian Hecht
2012-10-24 13:09 ` Will Deacon
2012-10-24 13:09 ` Will Deacon
2012-10-24 13:35 ` Bastian Hecht
2012-10-24 13:35 ` Bastian Hecht
2012-10-24 13:58 ` Will Deacon
2012-10-24 13:58 ` Will Deacon
2012-10-24 15:04 ` Bastian Hecht
2012-10-24 15:04 ` Bastian Hecht
2012-10-24 15:27 ` Will Deacon
2012-10-24 15:27 ` Will Deacon
2012-11-22 7:57 ` Artem Bityutskiy
2012-11-22 7:57 ` Artem Bityutskiy
2012-11-22 10:19 ` Will Deacon
2012-11-22 10:19 ` Will Deacon
2012-11-22 10:23 ` Artem Bityutskiy
2012-11-22 10:23 ` Artem Bityutskiy
2012-10-25 6:55 ` Artem Bityutskiy [this message]
2012-10-25 6:55 ` Artem Bityutskiy
2012-10-25 11:17 ` Will Deacon
2012-10-25 11:17 ` Will Deacon
2012-10-25 12:35 ` Mikael Pettersson
2012-10-25 12:35 ` Mikael Pettersson
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=1351148122.2507.63.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=hechtb@googlemail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=will.deacon@arm.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.