From: Jonathan Cameron <jic23@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>,
Jacob Pan <jacob.jun.pan@linux.intel.com>
Cc: Chen-Yu Tsai <wens@csie.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
"russianneuromancer @ ya . ru" <russianneuromancer@ya.ru>,
linux-iio@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] iio: adc: axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register modifications
Date: Sun, 8 Jan 2017 10:34:26 +0000 [thread overview]
Message-ID: <c9a8b592-9790-a0d7-7ec0-5d789cc34d6e@kernel.org> (raw)
In-Reply-To: <9c0346ee-753f-97ef-5f43-f7b561baf2e9@redhat.com>
On 08/01/17 10:15, Hans de Goede wrote:
> Hi,
>
> On 07-01-17 23:23, Jonathan Cameron wrote:
>> On 04/01/17 17:55, Jacob Pan wrote:
>>> On Tue, 3 Jan 2017 23:10:57 +0100
>>> Hans de Goede <hdegoede@redhat.com> wrote:
>>>
>>>>> It could have been a quirk we had to do on our platforms, I just
>>>>> cannot recall the details. Are you testing this on x86 platforms?
>>>>
>>>> Yes, I've successfully tested this on 2 different models cherrytrail
>>>> tablets.
>>>
>>> [Jacob Pan] I am ok with your change. I last tested on baytrail
>>> tablets, I don't know if you have one available to verify. That would
>>> be ideal.
>>>
>> Stable material? As I read this it is a fairly major fix, but we aren't
>> entirely sure there wasn't a reason on some platforms for this 'interesting'
>> corner of code?
>>
>> So basically are we sure this won't cause regressions? If so I'll take
>> it as a fix and mark for stable.
>
> The main consumer of the axp288_adc code is the axp288_fuel_gauge driver,
> which until now was not really functional. It depended on platform data
> being attached to its mfd device, and the provider of that platform data
> never got merged.
>
> I've got patches queued up for 4.11 fixing this. So in practice the chance
> of this patch causing regressions is close to 0 as so far it had no
> consumers, likewise adding a Cc: stable is not really useful.
Cool. I'll queue it for 4.11 as well then.
Applied to the togreg branch of iio.git which will be pushed out as testing for
the autobuilders to play with it.
Thanks,
Jonathan
>
> Regards,
>
> Hans
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-01-08 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 13:55 [PATCH] iio: adc: axp288: Drop bogus AXP288_ADC_TS_PIN_CTRL register modifications Hans de Goede
2016-12-14 15:00 ` Chen-Yu Tsai
2016-12-30 16:46 ` Jonathan Cameron
[not found] ` <1f31b2e7-90fa-0fb8-5f6e-a8ee2ddf69f7-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-12-30 18:15 ` Jacob Pan
2017-01-01 11:19 ` Hans de Goede
[not found] ` <054b52de-40fd-a879-7b8e-2d25fed18840-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2017-01-03 18:23 ` Jacob Pan
2017-01-03 22:10 ` Hans de Goede
2017-01-04 17:55 ` Jacob Pan
2017-01-07 22:23 ` Jonathan Cameron
2017-01-08 10:15 ` Hans de Goede
2017-01-08 10:34 ` 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=c9a8b592-9790-a0d7-7ec0-5d789cc34d6e@kernel.org \
--to=jic23@kernel.org \
--cc=hdegoede@redhat.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lars@metafoo.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=russianneuromancer@ya.ru \
--cc=wens@csie.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).