From: Hriday Hegde <hridayhegde1999@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alex Dewar <alex.dewar90@gmail.com>,
Sean Behan <codebam@riseup.net>,
Colin Ian King <colin.king@canonical.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: emxx_udc: Fixed coding style in places where lines should not end in '('
Date: Fri, 21 May 2021 00:43:16 +0530 [thread overview]
Message-ID: <a1c0247c-9cfe-b03a-86eb-a8313be25e55@gmail.com> (raw)
In-Reply-To: <20210520181838.GI1955@kadam>
On 20-05-2021 23:48, Dan Carpenter wrote:
> On Thu, May 20, 2021 at 10:46:57AM -0700, Hriday Hegde wrote:
>> The fixes were for the following checkpatch outputs:
>>
>> CHECK: Lines should not end with a '('
>> 1076: FILE: drivers/staging/emxx_udc/emxx_udc.c:1076:
>> + _nbu2ss_writel(
>>
>> CHECK: Lines should not end with a '('
>> 1228: FILE: drivers/staging/emxx_udc/emxx_udc.c:1228:
>> + length = _nbu2ss_readl(
>>
>> CHECK: Lines should not end with a '('
>> 1465: FILE: drivers/staging/emxx_udc/emxx_udc.c:1465:
>> + regdata = _nbu2ss_readl(
>>
>> Signed-off-by: Hriday Hegde <hridayhegde1999@gmail.com>
>> ---
>> drivers/staging/emxx_udc/emxx_udc.c | 10 ++++------
>> 1 file changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/staging/emxx_udc/emxx_udc.c b/drivers/staging/emxx_udc/emxx_udc.c
>> index 741147a4f0fe..8364316c1d25 100644
>> --- a/drivers/staging/emxx_udc/emxx_udc.c
>> +++ b/drivers/staging/emxx_udc/emxx_udc.c
>> @@ -1073,8 +1073,8 @@ static int _nbu2ss_epn_in_pio(struct nbu2ss_udc *udc, struct nbu2ss_ep *ep,
>> i_word_length = length / sizeof(u32);
>> if (i_word_length > 0) {
>> for (i = 0; i < i_word_length; i++) {
>> - _nbu2ss_writel(
>> - &preg->EP_REGS[ep->epnum - 1].EP_WRITE,
>> + _nbu2ss_writel(&preg->EP_REGS[ep->epnum - 1]
>> + .EP_WRITE,
>> p_buf_32->dw);
> No, this is worse than before.
>
> regards,
> dan carpenter
>
Yes sorry, didn't really take into account readability.
Thanks
Hriday
prev parent reply other threads:[~2021-05-20 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 17:46 Hriday Hegde
2021-05-20 18:00 ` Greg Kroah-Hartman
2021-05-20 19:11 ` Hriday Hegde
2021-05-20 18:18 ` Dan Carpenter
2021-05-20 19:13 ` Hriday Hegde [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=a1c0247c-9cfe-b03a-86eb-a8313be25e55@gmail.com \
--to=hridayhegde1999@gmail.com \
--cc=alex.dewar90@gmail.com \
--cc=codebam@riseup.net \
--cc=colin.king@canonical.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=memxor@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
Powered by JetHome