All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regmap: silence GCC warning
Date: Mon, 1 Oct 2012 20:11:58 +0100	[thread overview]
Message-ID: <20121001191158.GT4360@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1349118537.1414.22.camel@x61.thuisdomein>

On Mon, Oct 01, 2012 at 09:08:57PM +0200, Paul Bolle wrote:

> from cached registers"). The first release shipping that commit was
> v3.4. The log of a build of v3.4 using the oldest version of GCC (that
> Fedora used to build v3.4) I could find also contains this warning [0].
> They used gcc-4.6.3-2.fc16.x86_64 in that build [1].

> Perhaps I'll stumble on some build logs of v3.4 for which earlier
> versions of GCC were used. That might show whether or not earlier
> releases of GCC also print a warning for this code.

I'm using GCC 4.4.1 on ARM which seems quite happy.

  reply	other threads:[~2012-10-01 19:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-30 10:15 [PATCH] regmap: silence GCC warning Paul Bolle
2012-10-01 10:03 ` Mark Brown
2012-10-01 10:16   ` Paul Bolle
2012-10-01 10:19     ` Mark Brown
2012-10-01 10:32       ` Paul Bolle
2012-10-01 11:39         ` Mark Brown
2012-10-01 19:08           ` Paul Bolle
2012-10-01 19:11             ` Mark Brown [this message]
2012-10-03  0:11   ` Valdis.Kletnieks
2012-10-03  7:23     ` Paul Bolle
2012-10-03 11:06       ` Mark Brown
2012-10-05 22:20       ` Valdis.Kletnieks
2012-10-06  8:53         ` Mark Brown
2012-10-06  9:57           ` Paul Bolle
2012-10-08  1:14             ` Mark Brown
2012-10-08 20:06               ` [PATCH v2] " Paul Bolle
2012-10-12  6:26                 ` Mark Brown

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=20121001191158.GT4360@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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.