From: Greg KH <greg@kroah.com>
To: Lukas Schneider <lukas.s.schneider@fau.de>
Cc: leobras.c@gmail.com, digholebhagyashri@gmail.com,
bhanusreemahesh@gmail.com, daniel.vetter@ffwll.ch,
der_wolf_@web.de, payal.s.kshirsagar.98@gmail.com,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Jannik Moritz <jannik.moritz@fau.de>,
linux-kernel@i4.cs.fau.de
Subject: Re: [PATCH] fbtft: Cleanup line over 80 character warnings
Date: Thu, 27 Jun 2019 16:44:05 +0000 [thread overview]
Message-ID: <20190627164405.GB9692@kroah.com> (raw)
In-Reply-To: <20190627121240.31584-1-lukas.s.schneider@fau.de>
On Thu, Jun 27, 2019 at 02:12:40PM +0200, Lukas Schneider wrote:
> Cleanup the line over 80 character warnings, reported by checkpatch
>
> Signed-off-by: Lukas Schneider <lukas.s.schneider@fau.de>
> Signed-off-by: Jannik Moritz <jannik.moritz@fau.de>
> Cc: <linux-kernel@i4.cs.fau.de>
> ---
> drivers/staging/fbtft/fbtft-sysfs.c | 3 ++-
> drivers/staging/fbtft/fbtft.h | 26 ++++++++++++++++++++++----
> 2 files changed, 24 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/fbtft/fbtft-sysfs.c b/drivers/staging/fbtft/fbtft-sysfs.c
> index 2a5c630dab87..78d2b81ea2e7 100644
> --- a/drivers/staging/fbtft/fbtft-sysfs.c
> +++ b/drivers/staging/fbtft/fbtft-sysfs.c
> @@ -68,7 +68,8 @@ int fbtft_gamma_parse_str(struct fbtft_par *par, u32 *curves,
> ret = get_next_ulong(&curve_p, &val, " ", 16);
> if (ret)
> goto out;
> - curves[curve_counter * par->gamma.num_values + value_counter] = val;
> + curves[curve_counter * par->gamma.num_values
> + + value_counter] = val;
Ick, that's horrible to read now, right?
> value_counter++;
> }
> if (value_counter != par->gamma.num_values) {
> diff --git a/drivers/staging/fbtft/fbtft.h b/drivers/staging/fbtft/fbtft.h
> index 9b6bdb62093d..cddbfd4ffa10 100644
> --- a/drivers/staging/fbtft/fbtft.h
> +++ b/drivers/staging/fbtft/fbtft.h
> @@ -348,9 +348,25 @@ module_exit(fbtft_driver_module_exit);
>
> /* shorthand debug levels */
> #define DEBUG_LEVEL_1 DEBUG_REQUEST_GPIOS
> -#define DEBUG_LEVEL_2 (DEBUG_LEVEL_1 | DEBUG_DRIVER_INIT_FUNCTIONS | DEBUG_TIME_FIRST_UPDATE)
> -#define DEBUG_LEVEL_3 (DEBUG_LEVEL_2 | DEBUG_RESET | DEBUG_INIT_DISPLAY | DEBUG_BLANK | DEBUG_REQUEST_GPIOS | DEBUG_FREE_GPIOS | DEBUG_VERIFY_GPIOS | DEBUG_BACKLIGHT | DEBUG_SYSFS)
> -#define DEBUG_LEVEL_4 (DEBUG_LEVEL_2 | DEBUG_FB_READ | DEBUG_FB_WRITE | DEBUG_FB_FILLRECT | DEBUG_FB_COPYAREA | DEBUG_FB_IMAGEBLIT | DEBUG_FB_BLANK)
> +#define DEBUG_LEVEL_2 (DEBUG_LEVEL_1 | \
> + DEBUG_DRIVER_INIT_FUNCTIONS | \
> + DEBUG_TIME_FIRST_UPDATE)
> +#define DEBUG_LEVEL_3 (DEBUG_LEVEL_2 | \
> + DEBUG_RESET | \
> + DEBUG_INIT_DISPLAY | \
> + DEBUG_BLANK | \
> + DEBUG_REQUEST_GPIOS | \
> + DEBUG_FREE_GPIOS | \
> + DEBUG_VERIFY_GPIOS | \
> + DEBUG_BACKLIGHT | \
> + DEBUG_SYSFS)
> +#define DEBUG_LEVEL_4 (DEBUG_LEVEL_2 | \
> + DEBUG_FB_READ | \
> + DEBUG_FB_WRITE | \
> + DEBUG_FB_FILLRECT | \
> + DEBUG_FB_COPYAREA | \
> + DEBUG_FB_IMAGEBLIT | \
> + DEBUG_FB_BLANK)
> #define DEBUG_LEVEL_5 (DEBUG_LEVEL_3 | DEBUG_UPDATE_DISPLAY)
> #define DEBUG_LEVEL_6 (DEBUG_LEVEL_4 | DEBUG_LEVEL_5)
> #define DEBUG_LEVEL_7 0xFFFFFFFF
All of these special debug "levels" need to go away now that the drivers
are working, and just use the in-kernel debugging macros instead.
thanks,
greg k-h
prev parent reply other threads:[~2019-06-27 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 12:12 [PATCH] fbtft: Cleanup line over 80 character warnings Lukas Schneider
2019-06-27 12:26 ` Dan Carpenter
2019-06-27 16:44 ` Greg KH [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=20190627164405.GB9692@kroah.com \
--to=greg@kroah.com \
--cc=bhanusreemahesh@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=der_wolf_@web.de \
--cc=devel@driverdev.osuosl.org \
--cc=digholebhagyashri@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jannik.moritz@fau.de \
--cc=leobras.c@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@i4.cs.fau.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.s.schneider@fau.de \
--cc=payal.s.kshirsagar.98@gmail.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 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).