From: Greg KH <gregkh@linuxfoundation.org>
To: Pankaj Bharadiya <pankaj.bharadiya@gmail.com>
Cc: lidza.louina@gmail.com, devel@driverdev.osuosl.org,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: dgnc: Replace CamelCase namings with underscores.
Date: Mon, 17 Oct 2016 09:46:44 +0200 [thread overview]
Message-ID: <20161017074644.GB7010@kroah.com> (raw)
In-Reply-To: <1476647035-23634-1-git-send-email-pankaj.bharadiya@gmail.com>
On Mon, Oct 17, 2016 at 01:13:55AM +0530, Pankaj Bharadiya wrote:
> Replace CamelCase names with underscores to comply with the standard
> kernel coding style.
>
> Signed-off-by: Pankaj Bharadiya <pankaj.bharadiya@gmail.com>
> ---
> drivers/staging/dgnc/dgnc_tty.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/staging/dgnc/dgnc_tty.c b/drivers/staging/dgnc/dgnc_tty.c
> index ef9a45b..1a21902 100644
> --- a/drivers/staging/dgnc/dgnc_tty.c
> +++ b/drivers/staging/dgnc/dgnc_tty.c
> @@ -45,7 +45,7 @@
> /*
> * internal variables
> */
> -static unsigned char *dgnc_TmpWriteBuf;
> +static unsigned char *dgnc_tmp_write_buf;
Why not just fix the code to not have this variable at all? It's not
correct to have it from what I can tell...
Also, you modify many different variables all at once, can you please
just modify one at a time (one per patch), to make it more obvious it is
correct?
> /*
> * Default transparent print information.
> @@ -69,7 +69,7 @@
> * This defines a raw port at 9600 baud, 8 data bits, no parity,
> * 1 stop bit.
> */
> -static struct ktermios DgncDefaultTermios = {
> +static struct ktermios dgnc_default_termios = {
rename to "default_termios"?
No need to keep the driver name prefix on a static variable, right?
thanks,
greg k-h
next prev parent reply other threads:[~2016-10-17 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 19:43 Pankaj Bharadiya
2016-10-17 7:46 ` Greg KH [this message]
2016-10-18 2:28 ` Pankaj Bharadiya
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=20161017074644.GB7010@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.bharadiya@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
Powered by JetHome