From: Pritthijit Nath <pritthijit.nath@icloud.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: tvboxspy@gmail.com, devel@driverdev.osuosl.org,
oscar.carter@gmx.com, forest@alittletooquiet.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: vt6656: Fixed issue with alignment in rf.c
Date: Fri, 12 Feb 2021 02:32:51 +0530 [thread overview]
Message-ID: <a94be58e-b503-1fcf-7c5c-158ce7e2d188@icloud.com> (raw)
In-Reply-To: <YCWXH1MZy0cbDB3G@kroah.com>
On 12/02/21 2:14 am, Greg KH wrote:
> On Fri, Feb 12, 2021 at 02:07:50AM +0530, Pritthijit Nath wrote:
>> On 12/02/21 1:59 am, Greg KH wrote:
>>> On Thu, Feb 11, 2021 at 08:54:26PM +0530, Pritthijit Nath wrote:
>>>> This change fixes a checkpatch CHECK style issue for "Alignment should match open parenthesis".
>>>>
>>>> Signed-off-by: Pritthijit Nath <pritthijit.nath@icloud.com>
>>>> ---
>>>> drivers/staging/vt6656/rf.c | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/staging/vt6656/rf.c b/drivers/staging/vt6656/rf.c
>>>> index 5b8da06e3916..bcd4d467e03a 100644
>>>> --- a/drivers/staging/vt6656/rf.c
>>>> +++ b/drivers/staging/vt6656/rf.c
>>>> @@ -687,7 +687,7 @@ static int vnt_rf_set_txpower(struct vnt_private *priv, u8 power,
>>>>
>>>> if (hw_value < ARRAY_SIZE(vt3226d0_lo_current_table)) {
>>>> ret = vnt_rf_write_embedded(priv,
>>>> - vt3226d0_lo_current_table[hw_value]);
>>>> + vt3226d0_lo_current_table[hw_value]);
>>>> if (ret)
>>>> return ret;
>>>> }
>>>> --
>>>> 2.25.1
>>>
>>> Please run this change, with the changelog above, through
>>> checkpatch.pl, fix that, and resend.
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>>
>> This change fixes a checkpatch CHECK style issue for "Alignment should
>> match open parenthesis".
>>
>> Signed-off-by: Pritthijit Nath <pritthijit.nath@icloud.com>
>> ---
>> drivers/staging/vt6656/rf.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/staging/vt6656/rf.c b/drivers/staging/vt6656/rf.c
>> index 5b8da06e3916..bcd4d467e03a 100644
>> --- a/drivers/staging/vt6656/rf.c
>> +++ b/drivers/staging/vt6656/rf.c
>> @@ -687,7 +687,7 @@ static int vnt_rf_set_txpower(struct vnt_private *priv, u8 power,
>>
>> if (hw_value < ARRAY_SIZE(vt3226d0_lo_current_table)) {
>> ret = vnt_rf_write_embedded(priv,
>> - vt3226d0_lo_current_table[hw_value]);
>> + vt3226d0_lo_current_table[hw_value]);
>> if (ret)
>> return ret;
>> }
>
> I can't take this type of submission, do you see other patches submitted
> this way on the mailing list?
Actually I am having a hard time since this one's my first. I would really appreciate if you could be a little clear. Should I resend the entire patch as a new thread?
>
> Also, you have a trailing space in your changelog text :(
Thanks for pointing out. Yes, I have fixed the trailing space.
>
> thanks,
>
> greg k-h
>
next prev parent reply other threads:[~2021-02-11 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 15:24 Pritthijit Nath
2021-02-11 20:29 ` Greg KH
2021-02-11 20:37 ` Pritthijit Nath
2021-02-11 20:44 ` Greg KH
2021-02-11 21:02 ` Pritthijit Nath [this message]
2021-02-11 21:15 ` Greg KH
2021-02-11 21:26 Pritthijit Nath
2021-02-11 21:31 ` Greg KH
2021-02-11 21:37 Pritthijit Nath
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=a94be58e-b503-1fcf-7c5c-158ce7e2d188@icloud.com \
--to=pritthijit.nath@icloud.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oscar.carter@gmx.com \
--cc=tvboxspy@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
all inboxes | Powered by JetHome®