From: Greg KH <gregkh@linuxfoundation.org>
To: Gioh Kim <gi-oh.kim@profitbricks.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: greybus: es2.c: fix some coding style issues
Date: Thu, 9 Feb 2017 12:21:01 +0100 [thread overview]
Message-ID: <20170209112101.GA5775@kroah.com> (raw)
In-Reply-To: <1486638299-25999-1-git-send-email-gi-oh.kim@profitbricks.com>
On Thu, Feb 09, 2017 at 12:04:59PM +0100, Gioh Kim wrote:
> Fix two coding style issues:
> 1. line over 80 characters
> 2. Octal permissions are preffered than symbolic ones
I just said not to do this, why resend it?
Also, you forgot to include the correct people and mailing list on the
patch, please fix up.
greg k-h
prev parent reply other threads:[~2017-02-09 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 11:04 [PATCH] staging: greybus: es2.c: 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=20170209112101.GA5775@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=gi-oh.kim@profitbricks.com \
--cc=linux-kernel@vger.kernel.org \
/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.