From: Dan Carpenter <dan.carpenter@oracle.com>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: "Forest Bond" <forest@alittletooquiet.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Madhumitha Prabakaran" <madhumithabiw@gmail.com>,
"Yujia Qiao" <rapiz@foxmail.com>,
"Lucas Henneman" <lucas.henneman@linaro.org>,
"Aldas Taraškevičius" <aldas60@gmail.com>,
"Deepak R Varma" <mh12gx2825@gmail.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/3] staging: vt6655: fix camelcase in ldBmThreshold
Date: Tue, 5 Oct 2021 11:39:36 +0300 [thread overview]
Message-ID: <20211005083936.GW2048@kadam> (raw)
In-Reply-To: <20211004223200.70524-3-tomm.merciai@gmail.com>
On Tue, Oct 05, 2021 at 12:31:57AM +0200, Tommaso Merciai wrote:
> diff --git a/drivers/staging/vt6655/device.h b/drivers/staging/vt6655/device.h
> index 49e3d09480f2..e74372263e14 100644
> --- a/drivers/staging/vt6655/device.h
> +++ b/drivers/staging/vt6655/device.h
> @@ -215,7 +215,7 @@ struct vnt_private {
>
> bool bEncryptionEnable;
> bool bLongHeader;
> - bool short_slot_time;
> + bool bShortSlotTime;
Trolololol....
https://www.youtube.com/watch?v=2Z4m4lnjxkY
regards,
dan carpenter
next prev parent reply other threads:[~2021-10-05 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 22:31 [PATCH v6 0/3] staging: vt6655: replace camel case variables Tommaso Merciai
2021-10-04 22:31 ` [PATCH v6 1/3] staging: vt6655: fix camelcase in bShortSlotTime Tommaso Merciai
2021-10-04 22:31 ` [PATCH v6 2/3] staging: vt6655: fix camelcase in ldBmThreshold Tommaso Merciai
2021-10-05 8:39 ` Dan Carpenter [this message]
2021-10-05 20:30 ` Tommaso Merciai
2021-10-04 22:31 ` [PATCH v6 3/3] staging: vt6655: fix camelcase in PortOffset Tommaso Merciai
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=20211005083936.GW2048@kadam \
--to=dan.carpenter@oracle.com \
--cc=aldas60@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lucas.henneman@linaro.org \
--cc=madhumithabiw@gmail.com \
--cc=mh12gx2825@gmail.com \
--cc=rapiz@foxmail.com \
--cc=tomm.merciai@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