From: volery <sandro@volery.com>
To: rspringer@google.com, toddpoynor@google.com,
benchan@chromium.org, gregkh@linuxfoundation.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Fixed parentheses malpractice in apex_driver.c
Date: Fri, 6 Sep 2019 20:38:01 +0200 [thread overview]
Message-ID: <20190906183801.GA2456@volery> (raw)
There were some parentheses at the end of lines, which I took care of.
This is my first patch.
Signed-off-by: Sandro Volery <sandro@volery.com>
---
drivers/staging/gasket/apex_driver.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/gasket/apex_driver.c b/drivers/staging/gasket/apex_driver.c
index 464648ee2036..78ebd590f877 100644
--- a/drivers/staging/gasket/apex_driver.c
+++ b/drivers/staging/gasket/apex_driver.c
@@ -527,17 +527,20 @@ static ssize_t sysfs_show(struct device *device, struct device_attribute *attr,
switch (type) {
case ATTR_KERNEL_HIB_PAGE_TABLE_SIZE:
ret = scnprintf(buf, PAGE_SIZE, "%u\n",
- gasket_page_table_num_entries(
+ gasket_page_table_num_entries
+ (
gasket_dev->page_table[0]));
break;
case ATTR_KERNEL_HIB_SIMPLE_PAGE_TABLE_SIZE:
ret = scnprintf(buf, PAGE_SIZE, "%u\n",
- gasket_page_table_num_simple_entries(
+ gasket_page_table_num_simple_entries
+ (
gasket_dev->page_table[0]));
break;
case ATTR_KERNEL_HIB_NUM_ACTIVE_PAGES:
ret = scnprintf(buf, PAGE_SIZE, "%u\n",
- gasket_page_table_num_active_pages(
+ gasket_page_table_num_active_pages
+ (
gasket_dev->page_table[0]));
break;
default:
--
2.23.0
next reply other threads:[~2019-09-06 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 18:38 volery [this message]
2019-09-06 20:55 ` [PATCH] Fixed parentheses malpractice in apex_driver.c Joe Perches
2019-09-07 14:38 ` Dan Carpenter
2019-09-07 14:48 ` Sandro Volery
2019-09-07 14:52 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2019-09-07 15:34 Sandro Volery
2019-09-07 15:44 ` Joe Perches
2019-09-07 15:56 ` Sandro Volery
2019-09-07 16:08 ` Joe Perches
2019-09-07 16:12 ` Sandro Volery
2019-09-09 16:14 ` Joe Perches
2019-09-09 16:36 ` Sandro Volery
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=20190906183801.GA2456@volery \
--to=sandro@volery.com \
--cc=benchan@chromium.org \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rspringer@google.com \
--cc=toddpoynor@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.