From: Greg KH <gregkh@linuxfoundation.org>
To: Harsha Sharma <harshasharmaiitr@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
outreachy-kernel@googlegroups.com
Subject: Re: [PATCH v2] staging: rtl8723bs: Change coding style to (foo *bar)
Date: Mon, 11 Sep 2017 09:38:10 -0700 [thread overview]
Message-ID: <20170911163810.GA3423@kroah.com> (raw)
In-Reply-To: <1504977216-12686-1-git-send-email-harshasharmaiitr@gmail.com>
On Sat, Sep 09, 2017 at 10:43:36PM +0530, Harsha Sharma wrote:
> This coding style (foo *bar) is more common for the kernel code.
> Change foo* bar to foo *bar.
> Change foo * bar to foo *bar.
> Change (foo*) to (foo *).
>
> Signed-off-by: Harsha Sharma <harshasharmaiitr@gmail.com>
> ---
> Change in v2:
> -Updated log message and subject
Does not apply to my tree :(
next prev parent reply other threads:[~2017-09-11 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 17:13 [PATCH v2] staging: rtl8723bs: Change coding style to (foo *bar) Harsha Sharma
2017-09-11 16:38 ` Greg KH [this message]
2017-09-11 16:44 ` Harsha Sharma
2017-09-11 16:49 ` [Outreachy kernel] " Greg KH
2017-09-11 17:03 ` Julia Lawall
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=20170911163810.GA3423@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=harshasharmaiitr@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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.