From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] video: atmel_lcdfb: Use unique error messages in atmel_lcdfb_of_init()
Date: Mon, 06 Nov 2017 18:32:33 +0000 [thread overview]
Message-ID: <1509993153.2431.48.camel@perches.com> (raw)
In-Reply-To: <a768c806-8c15-5d74-02ac-38724482ac67@users.sourceforge.net>
On Mon, 2017-11-06 at 19:14 +0100, SF Markus Elfring wrote:
> A duplicate error message was used so far in this function implementation.
> Thus use a consistent message format instead together with property names
> where constant merging can be applied by the compiler in four cases.
[]
> diff --git a/drivers/video/fbdev/atmel_lcdfb.c b/drivers/video/fbdev/atmel_lcdfb.c
[]
> @@ -1021,6 +1021,8 @@ static void atmel_lcdfb_power_control_gpio(struct atmel_lcdfb_pdata *pdata, int
> gpio_set_value(og->gpio, on);
> }
>
> +static char const property_failure[] = "failed to get property %s\n";
Yuck. This makes it harder to grep the sources.
Just use the normal format string in each place.
> +
> static int atmel_lcdfb_of_init(struct atmel_lcdfb_info *sinfo)
> {
> struct fb_info *info = sinfo->info;
> @@ -1048,25 +1050,25 @@ static int atmel_lcdfb_of_init(struct atmel_lcdfb_info *sinfo)
>
> ret = of_property_read_u32(display_np, "bits-per-pixel", &var->bits_per_pixel);
> if (ret < 0) {
> - dev_err(dev, "failed to get property bits-per-pixel\n");
> + dev_err(dev, property_failure, "bits-per-pixel");
This likely doesn't even save any code size.
WARNING: multiple messages have this Message-ID (diff)
From: Joe Perches <joe@perches.com>
To: SF Markus Elfring <elfring@users.sourceforge.net>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2] video: atmel_lcdfb: Use unique error messages in atmel_lcdfb_of_init()
Date: Mon, 06 Nov 2017 10:32:33 -0800 [thread overview]
Message-ID: <1509993153.2431.48.camel@perches.com> (raw)
In-Reply-To: <a768c806-8c15-5d74-02ac-38724482ac67@users.sourceforge.net>
On Mon, 2017-11-06 at 19:14 +0100, SF Markus Elfring wrote:
> A duplicate error message was used so far in this function implementation.
> Thus use a consistent message format instead together with property names
> where constant merging can be applied by the compiler in four cases.
[]
> diff --git a/drivers/video/fbdev/atmel_lcdfb.c b/drivers/video/fbdev/atmel_lcdfb.c
[]
> @@ -1021,6 +1021,8 @@ static void atmel_lcdfb_power_control_gpio(struct atmel_lcdfb_pdata *pdata, int
> gpio_set_value(og->gpio, on);
> }
>
> +static char const property_failure[] = "failed to get property %s\n";
Yuck. This makes it harder to grep the sources.
Just use the normal format string in each place.
> +
> static int atmel_lcdfb_of_init(struct atmel_lcdfb_info *sinfo)
> {
> struct fb_info *info = sinfo->info;
> @@ -1048,25 +1050,25 @@ static int atmel_lcdfb_of_init(struct atmel_lcdfb_info *sinfo)
>
> ret = of_property_read_u32(display_np, "bits-per-pixel", &var->bits_per_pixel);
> if (ret < 0) {
> - dev_err(dev, "failed to get property bits-per-pixel\n");
> + dev_err(dev, property_failure, "bits-per-pixel");
This likely doesn't even save any code size.
next prev parent reply other threads:[~2017-11-06 18:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-05 13:10 [PATCH] video: atmel_lcdfb: Use common error handling code in atmel_lcdfb_of_init() SF Markus Elfring
2017-11-05 13:10 ` SF Markus Elfring
2017-11-06 8:40 ` Nicolas Ferre
2017-11-06 8:40 ` Nicolas Ferre
2017-11-06 8:40 ` Nicolas Ferre
2017-11-06 8:53 ` Dan Carpenter
2017-11-06 8:53 ` Dan Carpenter
2017-11-06 8:53 ` Dan Carpenter
2017-11-06 9:00 ` SF Markus Elfring
2017-11-06 9:00 ` SF Markus Elfring
2017-11-06 9:00 ` SF Markus Elfring
2017-11-06 9:53 ` Dan Carpenter
2017-11-06 9:53 ` Dan Carpenter
2017-11-06 9:53 ` Dan Carpenter
2017-11-06 9:32 ` SF Markus Elfring
2017-11-06 9:32 ` SF Markus Elfring
2017-11-06 9:32 ` SF Markus Elfring
2017-11-06 10:06 ` Nicolas Ferre
2017-11-06 10:06 ` Nicolas Ferre
2017-11-06 10:06 ` Nicolas Ferre
2017-11-06 18:14 ` [PATCH v2] video: atmel_lcdfb: Use unique error messages " SF Markus Elfring
2017-11-06 18:14 ` SF Markus Elfring
2017-11-06 18:14 ` SF Markus Elfring
2017-11-06 18:32 ` Joe Perches [this message]
2017-11-06 18:32 ` Joe Perches
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=1509993153.2431.48.camel@perches.com \
--to=joe@perches.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.