From: Johan Hovold <johan@kernel.org>
To: Lourdes Pedrajas <lu@pplo.net>
Cc: outreachy-kernel@googlegroups.com, rmfrfs@gmail.com,
johan@kernel.org, elder@kernel.org, gregkh@linuxfoundation.org,
vireshk@kernel.org
Subject: Re: [PATCH v2 1/2] staging: greybus: gpio: improve bit fields formatting.
Date: Mon, 16 Mar 2020 10:55:11 +0100 [thread overview]
Message-ID: <20200316095511.GV14211@localhost> (raw)
In-Reply-To: <88c5f940009f75813f026ebad57fc8865b242971.1584131593.git.lu@pplo.net>
On Sat, Mar 14, 2020 at 09:40:20PM +0100, Lourdes Pedrajas wrote:
> Fix the formatting of bit fields on structure gb_gpio_line, in order to
> not confuse them with indented labels.
> Issue found with checkpatch.
This is not an in issue found by checkpatch. Rather, you've found an
issue *with* checkpatch, which gets confused by these bit fields.
I'd just leave this as is, since there's nothing wrong with the code.
> Signed-off-by: Lourdes Pedrajas <lu@pplo.net>
> ---
> v2: log message correction
>
> drivers/staging/greybus/gpio.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/greybus/gpio.c b/drivers/staging/greybus/gpio.c
> index 36d99f9e419e..50e93a393dba 100644
> --- a/drivers/staging/greybus/gpio.c
> +++ b/drivers/staging/greybus/gpio.c
> @@ -20,9 +20,9 @@
> struct gb_gpio_line {
> /* The following has to be an array of line_max entries */
> /* --> make them just a flags field */
> - u8 active: 1,
> + u8 active: 1,
> direction: 1, /* 0 = output, 1 = input */
> - value: 1; /* 0 = low, 1 = high */
> + value: 1; /* 0 = low, 1 = high */
> u16 debounce_usec;
>
> u8 irq_type;
Johan
next prev parent reply other threads:[~2020-03-16 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 20:49 [PATCH 0/2] staging: greybus: simple formatting cleanup Lourdes Pedrajas
2020-03-13 20:49 ` [PATCH 1/2] staging: greybus: gpio: improve bit fields formatting Lourdes Pedrajas
2020-03-13 21:03 ` [Outreachy kernel] " Julia Lawall
2020-03-14 20:42 ` Lourdes Pedrajas
2020-03-16 9:55 ` Johan Hovold [this message]
2020-03-16 20:01 ` [PATCH v2 " Lourdes Pedrajas
2020-03-13 20:49 ` [PATCH 2/2] staging: greybus: hid: remove unneded braces Lourdes Pedrajas
2020-03-17 11:47 ` Greg KH
2020-03-17 17:07 ` Lourdes Pedrajas
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=20200316095511.GV14211@localhost \
--to=johan@kernel.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=lu@pplo.net \
--cc=outreachy-kernel@googlegroups.com \
--cc=rmfrfs@gmail.com \
--cc=vireshk@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 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.