From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/2] regmap: Use int rather than size_t for lengths when logging blocks
Date: Wed, 10 Aug 2011 00:19:24 +0900 [thread overview]
Message-ID: <20110809151923.GG15861@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110810010847.77e916a7780ffddd98d91f68@canb.auug.org.au>
On Wed, Aug 10, 2011 at 01:08:47AM +1000, Stephen Rothwell wrote:
> On Tue, 9 Aug 2011 17:00:04 +0900 Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> > x86_64 warns as size_t is not an int.
> > Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> > Stephen Rothwell <sfr@canb.auug.org.au>
> Reported-by?
Uh, yeah. That. Oops.
prev parent reply other threads:[~2011-08-09 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 8:00 [PATCH 1/2] regmap: Use int rather than size_t for lengths when logging blocks Mark Brown
2011-08-09 8:00 ` [PATCH 2/2] regmap: Fix type of field width specifiers for x86_64 Mark Brown
2011-08-09 15:08 ` [PATCH 1/2] regmap: Use int rather than size_t for lengths when logging blocks Stephen Rothwell
2011-08-09 15:19 ` Mark Brown [this message]
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=20110809151923.GG15861@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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.