From: Greg KH <gregkh@linuxfoundation.org>
To: Gioh Kim <gi-oh.kim@profitbricks.com>
Cc: thomas.petazzoni@free-electrons.com, noralf@tronnes.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: fbtft: fix some coding style issues
Date: Thu, 9 Feb 2017 12:21:18 +0100 [thread overview]
Message-ID: <20170209112118.GB5775@kroah.com> (raw)
In-Reply-To: <1486638241-25925-1-git-send-email-gi-oh.kim@profitbricks.com>
On Thu, Feb 09, 2017 at 12:04:01PM +0100, Gioh Kim wrote:
> There are many coding style issues.
> I fixed only obvious issues.
> Fixied issues:
> - Use 4 digit octal (0777) not decimal permissions
> - line over 80 characters
> - Avoid unnecessary line continuations
Again, only do one thing per patch.
Now dropped.
greg k-h
prev parent reply other threads:[~2017-02-09 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 11:04 [PATCH] staging: fbtft: fix some coding style issues Gioh Kim
2017-02-09 11:21 ` 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=20170209112118.GB5775@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gi-oh.kim@profitbricks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noralf@tronnes.org \
--cc=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).