From: Stephen Hemminger <stephen@networkplumber.org>
To: Santha Meena Ramamoorthy <santhameena13@gmail.com>
Cc: petr@vandrovec.name, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Staging: ncpfs: dir: fixed a bracket coding style issue
Date: Fri, 29 Dec 2017 19:52:34 -0800 [thread overview]
Message-ID: <20171229195234.176ea8ec@xeon-e3> (raw)
In-Reply-To: <1514590033-23503-1-git-send-email-santhameena13@gmail.com>
On Fri, 29 Dec 2017 15:27:13 -0800
Santha Meena Ramamoorthy <santhameena13@gmail.com> wrote:
> Fixed a coding style issue.
>
> Signed-off-by: Santha Meena Ramamoorthy <santhameena13@gmail.com>
Read the TODO please
prev parent reply other threads:[~2017-12-30 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 23:27 [PATCH] Staging: ncpfs: dir: fixed a bracket coding style issue Santha Meena Ramamoorthy
2017-12-30 3:52 ` Stephen Hemminger [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=20171229195234.176ea8ec@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
--cc=santhameena13@gmail.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.