devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	conor+dt@kernel.org, Conor Dooley <conor@kernel.org>,
	kauschluss@disroot.org
Subject: Re: [PATCH 1/3] iio: light: stk3310: relax chipid check warning
Date: Sun, 14 Jul 2024 08:51:25 +0000	[thread overview]
Message-ID: <05773f1b836aad0acb5acae35cca54a9@disroot.org> (raw)
In-Reply-To: <20240713130627.3d03290f@jic23-huawei>

On 2024-07-13 12:06, Jonathan Cameron wrote:
> On Fri, 12 Jul 2024 20:54:00 +0530
> Kaustabh Chakraborty <kauschluss@disroot.org> wrote:
> 
>> In order to allow newer devices which are compatible with existing
>> sensors, issuing a warning for an unknown chipid indicates that
>> something has gone wrong with the init process, which isn't ideal.
>> Swap it with a friendlier info message to get things right.
>> 
>> Suggested-by: Conor Dooley <conor@kernel.org>
>> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
> Give the patch series a cover letter next time as it makes it easy for
> people to comment on whole series together + gives the series a nice
> name in patchwork etc.

Sure, I assume I can add one in the next version, right?

> 
> Plus this isn't (I think) version 1.  So that should be in the patch naming.

Sorry, forgot adding v2 to the messages. I'll properly send a v3.

> 
> Actual change looks fine to me.
> 
> Thanks,
> 
> Jonathan
> 
>> ---
>>  drivers/iio/light/stk3310.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/drivers/iio/light/stk3310.c b/drivers/iio/light/stk3310.c
>> index e3470d6743ef..48a971de6a04 100644
>> --- a/drivers/iio/light/stk3310.c
>> +++ b/drivers/iio/light/stk3310.c
>> @@ -496,7 +496,7 @@ static int stk3310_init(struct iio_dev *indio_dev)
>>  
>>  	ret = stk3310_check_chip_id(chipid);
>>  	if (ret < 0)
>> -		dev_warn(&client->dev, "unknown chip id: 0x%x\n", chipid);
>> +		dev_info(&client->dev, "new unknown chip id: 0x%x\n", chipid);
>>  
>>  	state = STK3310_STATE_EN_ALS | STK3310_STATE_EN_PS;
>>  	ret = stk3310_set_state(data, state);

      reply	other threads:[~2024-07-14  8:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12 15:24 [PATCH 1/3] iio: light: stk3310: relax chipid check warning Kaustabh Chakraborty
2024-07-12 15:24 ` [PATCH 2/3] iio: light: stk3310: add support for stk3013 Kaustabh Chakraborty
2024-07-12 15:24 ` [PATCH 3/3] dt-bindings: iio: light: stk33xx: add compatible " Kaustabh Chakraborty
2024-07-13 12:06   ` Jonathan Cameron
2024-07-15 20:02     ` Kaustabh Chakraborty
2024-07-16 16:43       ` Jonathan Cameron
2024-07-17 15:58         ` Kaustabh Chakraborty
2024-07-20 12:45           ` Jonathan Cameron
2024-07-13 12:06 ` [PATCH 1/3] iio: light: stk3310: relax chipid check warning Jonathan Cameron
2024-07-14  8:51   ` Kaustabh Chakraborty [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=05773f1b836aad0acb5acae35cca54a9@disroot.org \
    --to=kauschluss@disroot.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --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).