From: Pritthijit Nath <pritthijit.nath@icloud.com>
To: vireshk@kernel.org, gregkh@linuxfoundation.org, johan@kernel.org,
elder@kernel.org
Cc: greybus-dev@lists.linaro.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
Pritthijit Nath <pritthijit.nath@icloud.com>
Subject: [PATCH 1/2] staging: greybus: Fixed alignment issue in hid.c
Date: Fri, 12 Feb 2021 13:48:34 +0530 [thread overview]
Message-ID: <20210212081835.9497-1-pritthijit.nath@icloud.com> (raw)
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;
--
2.25.1
next reply other threads:[~2021-02-12 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 8:18 Pritthijit Nath [this message]
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
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=20210212081835.9497-1-pritthijit.nath@icloud.com \
--to=pritthijit.nath@icloud.com \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®