From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jeremy Lacomis <j.lacomis@gmail.com>
Cc: sudipm.mukherjee@gmail.com, teddy.wang@siliconmotion.com,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: sm750fb: Fix coding style in ddk750_sii164.h
Date: Mon, 27 Nov 2017 12:46:22 +0300 [thread overview]
Message-ID: <20171127094622.phmx4ej2fljcytce@mwanda> (raw)
In-Reply-To: <20171125182636.15245-1-j.lacomis@gmail.com>
On Sat, Nov 25, 2017 at 01:26:35PM -0500, Jeremy Lacomis wrote:
> This patch to ddk750_sii164.h fixes line length warnings found by the
> checkpatch.pl script and reformats comments uniformly.
>
> Signed-off-by: Jeremy Lacomis <j.lacomis@gmail.com>
> ---
> drivers/staging/sm750fb/ddk750_sii164.h | 57 +++++++++++++--------------------
> 1 file changed, 22 insertions(+), 35 deletions(-)
>
> diff --git a/drivers/staging/sm750fb/ddk750_sii164.h b/drivers/staging/sm750fb/ddk750_sii164.h
> index 2e9a88cd6af3..393a3c5be3ae 100644
> --- a/drivers/staging/sm750fb/ddk750_sii164.h
> +++ b/drivers/staging/sm750fb/ddk750_sii164.h
> @@ -4,15 +4,20 @@
>
> #define USE_DVICHIP
>
> -/* Hot Plug detection mode structure */
> +/*
> + * Hot Plug detection mode structure:
> + * Disable Hot Plug output bit (always high).
> + * Use Monitor Detect Interrupt bit.
> + * Use Receiver Sense detect bit.
> + * Use Hot Plug detect bit.
> + */
> enum sii164_hot_plug_mode {
> - SII164_HOTPLUG_DISABLE = 0, /* Disable Hot Plug output bit (always high). */
> - SII164_HOTPLUG_USE_MDI, /* Use Monitor Detect Interrupt bit. */
> - SII164_HOTPLUG_USE_RSEN, /* Use Receiver Sense detect bit. */
> - SII164_HOTPLUG_USE_HTPLG /* Use Hot Plug detect bit. */
> + SII164_HOTPLUG_DISABLE = 0,
> + SII164_HOTPLUG_USE_MDI,
> + SII164_HOTPLUG_USE_RSEN,
> + SII164_HOTPLUG_USE_HTPLG
> };
I feel like this makes it less readable. The original was better.
regards,
dan carpenter
next prev parent reply other threads:[~2017-11-27 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 18:26 Jeremy Lacomis
2017-11-25 18:26 ` [PATCH 2/2] staging: sm750b: Fix coding style issues in sm750_accel.c Jeremy Lacomis
2017-11-25 21:38 ` Joe Perches
2017-11-27 9:46 ` Dan Carpenter [this message]
2017-11-27 10:45 ` [PATCH 1/2] staging: sm750fb: Fix coding style in ddk750_sii164.h Geert Uytterhoeven
2017-11-27 14:37 ` Jeremy Lacomis
2017-11-28 12:57 ` Greg KH
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=20171127094622.phmx4ej2fljcytce@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=j.lacomis@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=teddy.wang@siliconmotion.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
Powered by JetHome