[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200414135827.GB3593749@ulmo>
Date: Tue, 14 Apr 2020 15:58:27 +0200
From: Thierry Reding <thierry.reding@...il.com>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: u.kleine-koenig@...gutronix.de, linux-pwm@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] pwm: Add missing '\n' in log messages
On Sat, Apr 11, 2020 at 05:35:28PM +0200, Christophe JAILLET wrote:
> Message logged by 'dev_xxx()' or 'pr_xxx()' should end with a '\n'.
>
> Fixes: 3ad1f3a33286 ("pwm: Implement some checks for lowlevel drivers")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@...adoo.fr>
> ---
> drivers/pwm/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
> index 9973c442b455..bca04965bfe6 100644
> --- a/drivers/pwm/core.c
> +++ b/drivers/pwm/core.c
> @@ -537,7 +537,7 @@ static void pwm_apply_state_debug(struct pwm_device *pwm,
>
> if (!state->enabled && s2.enabled && s2.duty_cycle > 0)
> dev_warn(chip->dev,
> - "requested disabled, but yielded enabled with duty > 0");
> + "requested disabled, but yielded enabled with duty > 0\n");
>
> /* reapply the state that the driver reported being configured. */
> err = chip->ops->apply(chip, pwm, &s1);
I don't think this is strictly necessary any longer since the logging
functions are supposed to add these themselves nowadays. But I like the
consistency of this, so I'll apply this anyway.
Thanks,
Thierry
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists