From: Greg KH <gregkh@linuxfoundation.org>
To: Tanjuate Brunostar <tanjubrunostar0@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
outreachy@lists.linux.dev
Subject: Re: [PATCH] staging: vt6655: change variable name wTimeStampOff
Date: Mon, 31 Oct 2022 17:54:32 +0100 [thread overview]
Message-ID: <Y1/9yBVf4AcSp8Cs@kroah.com> (raw)
In-Reply-To: <Y1/fLjJmma28LudO@elroy-temp-vm.gaiao0uenmiufjlowqgp5yxwdh.gvxx.internal.cloudapp.net>
On Mon, Oct 31, 2022 at 02:43:58PM +0000, Tanjuate Brunostar wrote:
> The Linux coding style does not allow CamelCase variable naming.
That is a correct statement, but why say that here? We have
documentation that describes this already :)
Please read the kernel documentation for how to write a good changelog
text and resend this as a v2.
thanks,
greg k-h
prev parent reply other threads:[~2022-10-31 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 14:43 [PATCH] staging: vt6655: change variable name wTimeStampOff Tanjuate Brunostar
2022-10-31 16:54 ` 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=Y1/9yBVf4AcSp8Cs@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=tanjubrunostar0@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