From: Greg KH <gregkh@linuxfoundation.org>
To: Sandhya Bankar <bankarsandhya512@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH] Staging: lustre: Do not add space between function name and open parenthesis.
Date: Mon, 21 Mar 2016 21:45:32 -0400 [thread overview]
Message-ID: <20160322014532.GA9395@kroah.com> (raw)
In-Reply-To: <20160321145816.GA4355@sandhya>
On Mon, Mar 21, 2016 at 08:28:16PM +0530, Sandhya Bankar wrote:
> Do not add space between function name and open parenthesis.
>
> Signed-off-by: Sandhya Bankar <bankarsandhya512@gmail.com>
> ---
> .../staging/lustre/lustre/osc/osc_cl_internal.h | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/staging/lustre/lustre/osc/osc_cl_internal.h b/drivers/staging/lustre/lustre/osc/osc_cl_internal.h
> index d55d04d..3dfe5f6 100644
> --- a/drivers/staging/lustre/lustre/osc/osc_cl_internal.h
> +++ b/drivers/staging/lustre/lustre/osc/osc_cl_internal.h
> @@ -417,20 +417,20 @@ extern struct lu_context_key osc_session_key;
> int osc_lock_init(const struct lu_env *env,
> struct cl_object *obj, struct cl_lock *lock,
> const struct cl_io *io);
> -int osc_io_init (const struct lu_env *env,
> - struct cl_object *obj, struct cl_io *io);
> -int osc_req_init (const struct lu_env *env, struct cl_device *dev,
> - struct cl_req *req);
> +int osc_io_init(const struct lu_env *env,
> + struct cl_object *obj, struct cl_io *io);
> +int osc_req_init(const struct lu_env *env, struct cl_device *dev,
> + struct cl_req *req);
> struct lu_object *osc_object_alloc(const struct lu_env *env,
> const struct lu_object_header *hdr,
> struct lu_device *dev);
> int osc_page_init(const struct lu_env *env, struct cl_object *obj,
> struct cl_page *page, struct page *vmpage);
>
> -void osc_index2policy (ldlm_policy_data_t *policy, const struct cl_object *obj,
> - pgoff_t start, pgoff_t end);
> -int osc_lvb_print (const struct lu_env *env, void *cookie,
> - lu_printer_t p, const struct ost_lvb *lvb);
> +void osc_index2policy(ldlm_policy_data_t *policy, const struct cl_object *obj,
> + pgoff_t start, pgoff_t end);
> +int osc_lvb_print(const struct lu_env *env, void *cookie,
> + lu_printer_t p, const struct ost_lvb *lvb);
Does the code look better now? Before your patch, it looked much nicer,
don't you think?
thanks,
greg k-h
prev parent reply other threads:[~2016-03-22 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 14:58 [PATCH] Staging: lustre: Do not add space between function name and open parenthesis Sandhya Bankar
2016-03-22 1:45 ` 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=20160322014532.GA9395@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bankarsandhya512@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.