From: Karolina Stolarek <karolina.stolarek@intel.com>
To: Gilbert Adikankwu <gilbertadikankwu@gmail.com>
Cc: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
<outreachy@lists.linux.dev>, <forest@alittletooquiet.net>,
<gregkh@linuxfoundation.org>, <linux-staging@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] Rename variable bUpdateBBVGA, byCurrentCh, byCurPwr and byBBPreEDRSSI
Date: Tue, 17 Oct 2023 11:07:49 +0200 [thread overview]
Message-ID: <d77f35a3-5eec-d02f-459b-1968a58ff7d5@intel.com> (raw)
In-Reply-To: <ZS41jFfwBJ672Rb7@gilbert-PC>
On 17.10.2023 09:19, Gilbert Adikankwu wrote:
> On Tue, Oct 17, 2023 at 08:19:49AM +0200, Philipp Hortmann wrote:
>> On 10/17/23 00:58, Gilbert Adikankwu wrote:
>>> Make the variable names adhere to Linux kernel coding style and mute
>>> checkpatch.pl errors.
A small nit from my side -- "mute" suggests that you suppressed the
warning/error, but your changes fix them, so why now say "fix
checkpatch.pl errors"?
>>>
>>> Gilbert Adikankwu (4):
>>> staging: vt6655: Rename variable bUpdateBBVGA
>>> staging: vt6655: Rename variable byCurrentCh
>>> staging: vt6655: Rename variable byCurPwr
>>> staging: vt6655: Rename variable byBBPreEDRSSI
>>>
>>> drivers/staging/vt6655/baseband.c | 2 +-
>>> drivers/staging/vt6655/channel.c | 18 +++++++++---------
>>> drivers/staging/vt6655/device.h | 8 ++++----
>>> drivers/staging/vt6655/device_main.c | 8 ++++----
>>> drivers/staging/vt6655/dpc.c | 2 +-
>>> drivers/staging/vt6655/rf.c | 4 ++--
>>> 6 files changed, 21 insertions(+), 21 deletions(-)
>>>
>>
>> Hi,
>>
>> - if (priv->byCurrentCh == ch->hw_value)
>> + if (priv->current_ch == ch->hw_value)^M
>> return ret;
>>
>> ERROR: DOS line endings
>>
>> What does the "^M" at the end of the new line?
>> Did you run checkpatch on your patches?
>>
>> Thanks
>>
>> Bye
>>
>> Philipp
>
> Hello,
>
> I do not know what this error means. If anything, I'm surprised there is
> an error. checkpatch is hooked to my git commit and all the patches
> built cleanly on my machine. I will resend now.
I'm not seeing that error when the patch is applied. You could
double-check the patch files before sending by calling checkpatch.pl on
them directly.
This could be also because of how some email clients change the endings
on download, like Thunderbird, and the patch itself might be fine.
All the best,
Karolina
>
> Thanks
> Gilbert
>
next prev parent reply other threads:[~2023-10-17 9:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 22:58 [PATCH 0/4] Rename variable bUpdateBBVGA, byCurrentCh, byCurPwr and byBBPreEDRSSI Gilbert Adikankwu
2023-10-16 22:58 ` [PATCH 1/4] staging: vt6655: Rename variable bUpdateBBVGA Gilbert Adikankwu
2023-10-17 4:48 ` Julia Lawall
2023-10-17 7:30 ` Gilbert Adikankwu
2023-10-17 7:33 ` Julia Lawall
2023-10-16 22:58 ` [PATCH 2/4] staging: vt6655: Rename variable byCurrentCh Gilbert Adikankwu
2023-10-16 22:58 ` [PATCH 3/4] staging: vt6655: Rename variable byCurPwr Gilbert Adikankwu
2023-10-16 22:58 ` [PATCH 4/4] staging: vt6655: Rename variable byBBPreEDRSSI Gilbert Adikankwu
2023-10-17 6:19 ` [PATCH 0/4] Rename variable bUpdateBBVGA, byCurrentCh, byCurPwr and byBBPreEDRSSI Philipp Hortmann
2023-10-17 7:19 ` Gilbert Adikankwu
2023-10-17 9:07 ` Karolina Stolarek [this message]
2023-10-17 13:40 ` Greg KH
2023-10-17 18:01 ` Philipp Hortmann
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=d77f35a3-5eec-d02f-459b-1968a58ff7d5@intel.com \
--to=karolina.stolarek@intel.com \
--cc=forest@alittletooquiet.net \
--cc=gilbertadikankwu@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=philipp.g.hortmann@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