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 8/8] power: supply: fix wrong interpretation of register value
Date: Mon, 24 Oct 2022 16:37:19 +0200 [thread overview]
Message-ID: <3769d202-334b-28f7-df96-a032301e1b96@gmail.com> (raw)
In-Reply-To: <CAHp75Veht22nPGyZGp4G0yGvYm4hyjZGvX4fdz4qCz7VUJcEdg@mail.gmail.com>
On 24/10/22 16:18, Andy Shevchenko wrote:
> On Mon, Oct 24, 2022 at 5:07 PM saravanan sekar <sravanhome@gmail.com> wrote:
>>
>> On 24/10/22 15:50, Andy Shevchenko wrote:
>>> On Mon, Oct 24, 2022 at 4:50 PM Andy Shevchenko
>>> <andy.shevchenko@gmail.com> wrote:
>>>> On Mon, Oct 24, 2022 at 4:28 PM Saravanan Sekar <sravanhome@gmail.com> wrote:
>>>>>
>>>>> fix wrong interpretation of bitwise as hex
>>>
>>> Maybe you can replace 0x with 0b instead?
>>>
>>
>> Ok, I consider to changes as "fix the register value interpretation as
>> 0x instead of 0b" does it fits !!
>
> No, it doesn't because there is no evidence of 0b in use. I suggested
> to use 0b in the code (as the part of your change) instead of
> switching to hex.
>
Ok, I guess re-phrase of commit message shall solve the conflict. I feel
use of 0x in code is fine.
I will edit the commit message as "fix the switch case to match the
register values"
Thanks,
Saravanan
prev parent reply other threads:[~2022-10-24 15:58 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
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 [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=3769d202-334b-28f7-df96-a032301e1b96@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).