[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ehobtvxpi4zjzt6wenxklqg4fcili3mugb2nqhwnvtsldqyzid@ayk2cuqn4k7s>
Date: Mon, 9 Sep 2024 21:29:48 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Thomas Richard <thomas.richard@...tlin.com>
Cc: Lee Jones <lee@...nel.org>, Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>, Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-i2c@...r.kernel.org, linux-watchdog@...r.kernel.org, thomas.petazzoni@...tlin.com,
blake.vermeer@...sight.com
Subject: Re: [PATCH 3/5] i2c: Congatec Board Controller i2c bus driver
Hi Thomas,
> >> + if (bus_frequency > CGBC_I2C_FREQ_MAX_HZ ||
> >> + bus_frequency < CGBC_I2C_FREQ_MIN_HZ) {
> >> + dev_warn(i2c->dev, "invalid frequency %u, using default\n", bus_frequency);
> >
> > should this rather be a dev_info()? (supernit: please start with
> > capital leter).
>
> The driver i2c-xlp9xx has a similar message [1] and it uses a dev_warn().
> So I don't know.
> If you think dev_info() is more relevant in this case, I'll change it.
> Supernit will be fixed in next iteration.
Not a binding comment, it looks to me more a dev_info(), if you
prefer you can use dev_warn(). In any case, at this stage, I
don't see this printed anywhere :-)
Thanks,
Andi
Powered by blists - more mailing lists