From: Greg KH <gregkh@linuxfoundation.org>
To: anushkacharu9@gmail.com
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: gasket: Create a new variable to improve readability
Date: Sun, 17 Mar 2019 11:13:37 +0100 [thread overview]
Message-ID: <20190317101337.GD26906@kroah.com> (raw)
In-Reply-To: <20190316195427.2673-1-anushkacharu9@gmail.com>
On Sun, Mar 17, 2019 at 01:24:27AM +0530, anushkacharu9@gmail.com wrote:
> From: Anushka Shukla <anushkacharu9@gmail.com>
>
> - Define a new variable temp_table.
> - Modify it to maintain Linux Kernel Coding style.
What is "it" here?
>
> Signed-off-by: Anushka Shukla <anushkacharu9@gmail.com>
> ---
> drivers/staging/gasket/apex_driver.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/gasket/apex_driver.c b/drivers/staging/gasket/apex_driver.c
> index 7c2ffa467557..d0fffb51c9c4 100644
> --- a/drivers/staging/gasket/apex_driver.c
> +++ b/drivers/staging/gasket/apex_driver.c
> @@ -526,21 +526,22 @@ static ssize_t sysfs_show(struct device *device, struct device_attribute *attr,
> }
>
> type = (enum sysfs_attribute_type)gasket_attr->data.attr_type;
> + struct gasket_page_table *temp_table = gasket_dev->page_table[0]
Did you build this code? The compiler should have complained a lot
about this :(
> switch (type) {
> case ATTR_KERNEL_HIB_PAGE_TABLE_SIZE:
> ret = scnprintf(buf, PAGE_SIZE, "%u\n",
> - gasket_page_table_num_entries
> - (gasket_dev->page_table[0]));
> + gasket_page_table_num_entries(temp_table);
> +
Always run your patches through checkpatch.pl before sending them out,
so that a maintainer does not have to tell you to run them through
checkpatch.pl :)
thanks,
greg k-h
prev parent reply other threads:[~2019-03-17 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 19:54 [PATCH] Staging: gasket: Create a new variable to improve readability anushkacharu9
2019-03-17 10:13 ` Greg KH [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=20190317101337.GD26906@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anushkacharu9@gmail.com \
--cc=outreachy-kernel@googlegroups.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.