From: Karolina Drobnik <karolinadrobnik@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: outreachy-kernel@googlegroups.com, gregkh@linuxfoundation.org,
forest@alittletooquiet.net, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] [PATCH 2/5] staging: vt6655: Rename `byInitCount` variable
Date: Mon, 25 Oct 2021 10:38:46 +0100 [thread overview]
Message-ID: <4a0993774f75323c803f7b07ff9825d7beb6d95b.camel@gmail.com> (raw)
In-Reply-To: <20211022164011.GB464908@alison-desk>
Hi Alison,
On Fri, 2021-10-22 at 09:40 -0700, Alison Schofield wrote:
> On Fri, Oct 22, 2021 at 10:37:15AM +0100, Karolina Drobnik wrote:
> > Drop Hungarian notation in `byInitCount` variable in
> > `RFvWriteWakeProgSyn` function. Change it to use snake case.
> >
> > Fix issue detected by checkpatch.pl:
> > CHECK: Avoid CamelCase: <byInitCount>
>
> Hi Karolina,
>
> This comment is for all the patches.
>
> Commit msg:
> We've got plenty of space on that line, how about:
> "Rename byInitCount init_count"
>
> (I say this because when someone searches by the oneliners it's
> nice to give as many keywords as possible - within the line limit)
Ok, will do my best to include it in my upcoming patchset.
> Commit log:
> The log (why this patch is important) seems to be saying that
> snake case is the fix for Hungarian notation. I don't think that
> is completely true. Snake case avoids the camel case of Hungarian
> notation, but we are also dropping the type descriptor which is
> another signature of Hungarian notation.
>
> Perhaps this would be more direct:
>
> To align with the kernel coding style, remove the type from
> the variable name and do not use CamelCase.
Ok, I'll use this format from now on.
Thanks,
Karolina
next prev parent reply other threads:[~2021-10-25 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 9:37 [PATCH 0/5] staging: vt6655: `RFvWriteWakeProgSyn` variables rename Karolina Drobnik
2021-10-22 9:37 ` [PATCH 1/5] staging: vt6655: Rename `ii` variable Karolina Drobnik
2021-10-22 9:37 ` [PATCH 2/5] staging: vt6655: Rename `byInitCount` variable Karolina Drobnik
2021-10-22 16:40 ` [Outreachy kernel] " Alison Schofield
2021-10-25 9:38 ` Karolina Drobnik [this message]
2021-10-22 9:37 ` [PATCH 3/5] staging: vt6655: Rename `bySleepCount` variable Karolina Drobnik
2021-10-22 9:37 ` [PATCH 4/5] staging: vt6655: Rename `uChannel` variable Karolina Drobnik
2021-10-22 9:37 ` [PATCH 5/5] staging: vt6655: Rename `byRFType` variable Karolina Drobnik
2021-10-22 14:26 ` [Outreachy kernel] " Praveen Kumar
2021-10-22 15:58 ` Karolina Drobnik
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=4a0993774f75323c803f7b07ff9825d7beb6d95b.camel@gmail.com \
--to=karolinadrobnik@gmail.com \
--cc=alison.schofield@intel.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy-kernel@googlegroups.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
all inboxes | Powered by JetHome®