From: Jonathan Cameron <jic23@kernel.org>
To: Hartmut Knaack <knaack.h@gmx.de>, linux-iio@vger.kernel.org
Cc: Erik.Habbinga@schneider-electric.com
Subject: Re: [PATCH] iio:adc:max1363 incorrect resolutions for max11604, max11605, max11610 and max11611.
Date: Sun, 25 May 2014 12:07:47 +0100 [thread overview]
Message-ID: <5381CF03.4010005@kernel.org> (raw)
In-Reply-To: <53810894.2000806@gmx.de>
On 24/05/14 22:01, Hartmut Knaack wrote:
> Jonathan Cameron schrieb:
>> Reported-by: Erik Habbinga <Erik.Habbinga@schneider-electric.com>
>> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
> Acked-by: Hartmut Knaack <knaack.h@gmx.de>
Thanks,
Given the late stage in the cycle and the relatively minor nature of this
bug I've applied it to the togreg tree for the next merge window.
Jonathan
>> ---
>> drivers/iio/adc/max1363.c | 16 ++++++++--------
>> 1 file changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/iio/adc/max1363.c b/drivers/iio/adc/max1363.c
>> index 9cf3229..1b3b74b 100644
>> --- a/drivers/iio/adc/max1363.c
>> +++ b/drivers/iio/adc/max1363.c
>> @@ -1252,8 +1252,8 @@ static const struct max1363_chip_info max1363_chip_info_tbl[] = {
>> .num_modes = ARRAY_SIZE(max1238_mode_list),
>> .default_mode = s0to11,
>> .info = &max1238_info,
>> - .channels = max1238_channels,
>> - .num_channels = ARRAY_SIZE(max1238_channels),
>> + .channels = max1038_channels,
>> + .num_channels = ARRAY_SIZE(max1038_channels),
>> },
>> [max11605] = {
>> .bits = 8,
>> @@ -1262,8 +1262,8 @@ static const struct max1363_chip_info max1363_chip_info_tbl[] = {
>> .num_modes = ARRAY_SIZE(max1238_mode_list),
>> .default_mode = s0to11,
>> .info = &max1238_info,
>> - .channels = max1238_channels,
>> - .num_channels = ARRAY_SIZE(max1238_channels),
>> + .channels = max1038_channels,
>> + .num_channels = ARRAY_SIZE(max1038_channels),
>> },
>> [max11606] = {
>> .bits = 10,
>> @@ -1312,8 +1312,8 @@ static const struct max1363_chip_info max1363_chip_info_tbl[] = {
>> .num_modes = ARRAY_SIZE(max1238_mode_list),
>> .default_mode = s0to11,
>> .info = &max1238_info,
>> - .channels = max1238_channels,
>> - .num_channels = ARRAY_SIZE(max1238_channels),
>> + .channels = max1138_channels,
>> + .num_channels = ARRAY_SIZE(max1138_channels),
>> },
>> [max11611] = {
>> .bits = 10,
>> @@ -1322,8 +1322,8 @@ static const struct max1363_chip_info max1363_chip_info_tbl[] = {
>> .num_modes = ARRAY_SIZE(max1238_mode_list),
>> .default_mode = s0to11,
>> .info = &max1238_info,
>> - .channels = max1238_channels,
>> - .num_channels = ARRAY_SIZE(max1238_channels),
>> + .channels = max1138_channels,
>> + .num_channels = ARRAY_SIZE(max1138_channels),
>> },
>> [max11612] = {
>> .bits = 12,
>
prev parent reply other threads:[~2014-05-25 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 12:04 [PATCH] iio:adc:max1363 incorrect resolutions for max11604, max11605, max11610 and max11611 Jonathan Cameron
2014-05-24 21:01 ` Hartmut Knaack
2014-05-25 11:07 ` Jonathan Cameron [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=5381CF03.4010005@kernel.org \
--to=jic23@kernel.org \
--cc=Erik.Habbinga@schneider-electric.com \
--cc=knaack.h@gmx.de \
--cc=linux-iio@vger.kernel.org \
/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).