From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: sameo@linux.intel.com, patches@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: arizona: Use correct array for ARRAY_SIZE in mfd_add_devices call
Date: Thu, 25 Oct 2012 17:02:09 +0100 [thread overview]
Message-ID: <20121025160208.GM18814@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20121025141244.GA31078@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Thu, Oct 25, 2012 at 03:12:44PM +0100, Charles Keepax wrote:
> wm5102_devs array was used for ARRAY_SIZE whilst adding the wm5110
> devices. This change corrects this to get the size from the wm5110_devs
> array. As both arrays are the same size no issues should have been
> caused by this bug.
Reviewed-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-10-25 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 14:12 Charles Keepax
2012-10-25 16:02 ` 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=20121025160208.GM18814@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=sameo@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome