From: Greg KH <gregkh@linuxfoundation.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: devel@driverdev.osuosl.org, elder@kernel.org, vireshk@kernel.org,
johan@kernel.org, linux-kernel@vger.kernel.org,
greybus-dev@lists.linaro.org,
Pritthijit Nath <pritthijit.nath@icloud.com>
Subject: Re: [PATCH 1/2] staging: greybus: Fixed alignment issue in hid.c
Date: Fri, 12 Feb 2021 10:36:57 +0100 [thread overview]
Message-ID: <YCZMOQdVDk7mStBy@kroah.com> (raw)
In-Reply-To: <20210212092130.cxo6tuess6msf4kb@vireshk-i7>
On Fri, Feb 12, 2021 at 02:51:30PM +0530, Viresh Kumar wrote:
> On 12-02-21, 10:17, Greg KH wrote:
> > On Fri, Feb 12, 2021 at 02:39:26PM +0530, Viresh Kumar wrote:
> > > On 12-02-21, 13:48, 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/greybus/hid.c | 4 ++--
> > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/staging/greybus/hid.c b/drivers/staging/greybus/hid.c
> > > > index ed706f39e87a..a56c3fb5d35a 100644
> > > > --- a/drivers/staging/greybus/hid.c
> > > > +++ b/drivers/staging/greybus/hid.c
> > > > @@ -221,8 +221,8 @@ static void gb_hid_init_reports(struct gb_hid *ghid)
> > > > }
> > > >
> > > > static int __gb_hid_get_raw_report(struct hid_device *hid,
> > > > - unsigned char report_number, __u8 *buf, size_t count,
> > > > - unsigned char report_type)
> > > > + unsigned char report_number, __u8 *buf, size_t count,
> > > > + unsigned char report_type)
> > > > {
> > > > struct gb_hid *ghid = hid->driver_data;
> > > > int ret;
> > >
> > > I can't even count the number of attempts we have seen in previous
> > > years to make checkpatch --strict happy for greybus.
> > >
> > > I say we make this change once and for all across greybus, so we don't
> > > have to review or NAK someone afterwards.
> > >
> > > Should I send a patch for this ?
> >
> > Sure, but note that over time, checkpatch adds new things so there will
> > always be something to change in here, until we move it out of the
> > drivers/staging/ area :)
>
> Right, though I wasn't worried about other checkpatch warning but
> specially the "alignment - parenthesis" one. Everyone (specially
> newbies) want to fix that everywhere :)
Sure, fix it up "right" if you want to, I'll take coding style fixes
from anyone :)
next prev parent reply other threads:[~2021-02-12 9:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 8:18 [PATCH 1/2] staging: greybus: Fixed alignment issue in hid.c Pritthijit Nath
2021-02-12 8:18 ` [PATCH 2/2] staging: greybus: Fixed a misspelling " Pritthijit Nath
2021-02-12 8:44 ` Johan Hovold
2021-02-12 8:54 ` Greg KH
2021-02-12 9:07 ` Viresh Kumar
2021-02-12 9:09 ` [PATCH 1/2] staging: greybus: Fixed alignment issue " Viresh Kumar
2021-02-12 9:17 ` Greg KH
2021-02-12 9:21 ` Viresh Kumar
2021-02-12 9:36 ` Greg KH [this message]
2021-02-12 9:52 ` Johan Hovold
2021-02-12 9:55 ` Viresh Kumar
2021-02-12 10:06 ` Johan Hovold
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=YCZMOQdVDk7mStBy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pritthijit.nath@icloud.com \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
/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