devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: saravanan sekar <sravanhome@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: sre@kernel.org, lee.jones@linaro.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, jic23@kernel.org,
	lars@metafoo.de, linux-pm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 6/8] power: supply: fix failed to get iio channel by device name
Date: Mon, 24 Oct 2022 16:02:21 +0200	[thread overview]
Message-ID: <049e0cf3-49b9-ed25-c595-06de22117f1a@gmail.com> (raw)
In-Reply-To: <CAHp75VcvZ9drkFfbpVJFz0UWQvOMgAu3+JmV4HvOG3dPKDoN5w@mail.gmail.com>

On 24/10/22 15:49, Andy Shevchenko wrote:
> On Mon, Oct 24, 2022 at 4:28 PM Saravanan Sekar <sravanhome@gmail.com> wrote:
>>
>> The mfd cell devices name populated on sysfs entry is dynamically derived
>> from an auto instance which introduced a regression. As a result
>> mpc2629_charger driver failed to get adc channel because of iio consumer
>> name mismatch with the sysfs.
>>
>> /sys/class/i2c-adapter/i2c-1/mp2629_adc.0.auto/
>> /sys/class/i2c-adapter/i2c-1/mp2629_charger.1.auto/
>>
>> Fixes: 466a62d7642f(mfd: core: Make a best effort attempt to match devices)
> 
> Wrong Fixes tag format, moreover the fixes should be grouped at the
> beginning of the series, so it will be visible and splittable based on
> this property.

Thanks for quick review Andy, I will correct fixes tag format and group 
all the fixes beginning of series in v5.

Thanks,
Saravanan



  reply	other threads:[~2022-10-24 16:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 13:27 [PATCH v4 0/8] Add support for mp2733 battery charger Saravanan Sekar
2022-10-24 13:27 ` [PATCH v4 1/8] iio: adc: mp2629: fix wrong comparison of channel Saravanan Sekar
2022-10-24 13:27 ` [PATCH v4 2/8] mfd: mp2629: Add support for mps mp2733 battery charger Saravanan Sekar
2022-10-24 13:27 ` [PATCH v4 3/8] iio: adc: mp2629: restrict input voltage mask for mp2629 Saravanan Sekar
2022-10-24 13:27 ` [PATCH v4 4/8] power: supply: Add support for mp2733 battery charger Saravanan Sekar
2022-10-28 14:06   ` Sebastian Reichel
2022-10-24 13:27 ` [PATCH v4 5/8] power: supply: mp2629: Add USB fast charge settings Saravanan Sekar
2022-10-28 14:07   ` Sebastian Reichel
2022-10-24 13:27 ` [PATCH v4 6/8] power: supply: fix failed to get iio channel by device name Saravanan Sekar
2022-10-24 13:49   ` Andy Shevchenko
2022-10-24 14:02     ` saravanan sekar [this message]
2022-10-28 14:05       ` Sebastian Reichel
2022-10-24 13:27 ` [PATCH v4 7/8] iio: adc: mp2629: fix potential array out of bound access Saravanan Sekar
2022-10-24 13:27 ` [PATCH v4 8/8] power: supply: fix wrong interpretation of register value Saravanan Sekar
2022-10-24 13:50   ` Andy Shevchenko
2022-10-24 13:50     ` Andy Shevchenko
2022-10-24 14:07       ` saravanan sekar
2022-10-24 14:18         ` Andy Shevchenko
2022-10-24 14:37           ` saravanan sekar

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=049e0cf3-49b9-ed25-c595-06de22117f1a@gmail.com \
    --to=sravanhome@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sre@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).