From: Johan Hovold <johan@kernel.org>
To: Gioh Kim <gi-oh.kim@profitbricks.com>
Cc: johan@kernel.org, gregkh@linuxfoundation.org, elder@kernel.org,
greybus-dev@lists.linaro.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: greybus: fix symbolic permission coding style issues
Date: Mon, 13 Feb 2017 11:12:01 +0100 [thread overview]
Message-ID: <20170213101201.GA27275@localhost> (raw)
In-Reply-To: <1486657812-7948-2-git-send-email-gi-oh.kim@profitbricks.com>
On Thu, Feb 09, 2017 at 05:30:12PM +0100, Gioh Kim wrote:
> Fix "Octal permissions are preffered than symbolic ones" issues.
>
> Signed-off-by: Gioh Kim <gi-oh.kim@profitbricks.com>
Acked-by: Johan Hovold <johan@kernel.org>
next prev parent reply other threads:[~2017-02-13 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 16:30 [PATCH 1/2] staging: greybus: fix "line over 80 characters" coding style issues Gioh Kim
2017-02-09 16:30 ` [PATCH 2/2] staging: greybus: fix symbolic permission " Gioh Kim
2017-02-13 10:12 ` Johan Hovold [this message]
2017-02-13 10:41 ` [PATCH 1/2] staging: greybus: fix "line over 80 characters" " Johan Hovold
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=20170213101201.GA27275@localhost \
--to=johan@kernel.org \
--cc=devel@driverdev.osuosl.org \
--cc=elder@kernel.org \
--cc=gi-oh.kim@profitbricks.com \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--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.