From: "Kershner, David A" <David.Kershner@unisys.com>
To: Derek Robson <robsonde@gmail.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Sell, Timothy C" <Timothy.Sell@unisys.com>
Cc: *S-Par-Maintainer <SParMaintainer@unisys.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file permissions
Date: Sat, 7 Jan 2017 04:54:21 +0000 [thread overview]
Message-ID: <BLUPR07MB2282E46A8CBFAE9B2A11AA5F0620@BLUPR07MB228.namprd07.prod.outlook.com> (raw)
In-Reply-To: <cover.1483760409.git.robsonde@gmail.com>
> -----Original Message-----
> From: Derek Robson [mailto:robsonde@gmail.com]
> Sent: Friday, January 6, 2017 10:48 PM
> To: Kershner, David A <David.Kershner@unisys.com>;
> gregkh@linuxfoundation.org; Sell, Timothy C <Timothy.Sell@unisys.com>
> Cc: *S-Par-Maintainer <SParMaintainer@unisys.com>;
> devel@driverdev.osuosl.org; linux-kernel@vger.kernel.org; Derek Robson
> <robsonde@gmail.com>
> Subject: [PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file
> permissions
>
> Two files change in style fix, changes are octal file permissions.
>
Series looks fine to me and runs on top of the s-Par firmware.
Acked-by: David Kershner <david.kershner@unisys.com>
> Derek Robson (2):
> Staging: unisys: visorbus: style fix, using octal file permissions
> Staging: unisys: visorbus: style fix, using octal file permissions
>
> drivers/staging/unisys/visorbus/visorbus_main.c | 6 +++---
> drivers/staging/unisys/visorbus/visorchipset.c | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> --
> 2.11.0
next prev parent reply other threads:[~2017-01-07 4:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 3:48 [PATCH 0/2] Staging: unisys: visorbus: style fix, using octal file permissions Derek Robson
2017-01-07 3:48 ` [PATCH 1/2] " Derek Robson
2017-01-07 3:48 ` [PATCH 2/2] " Derek Robson
2017-01-07 4:54 ` Kershner, David A [this message]
2017-01-07 7:44 ` [PATCH 0/2] " Greg KH
2017-01-09 20:17 ` Andy Shevchenko
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=BLUPR07MB2282E46A8CBFAE9B2A11AA5F0620@BLUPR07MB228.namprd07.prod.outlook.com \
--to=david.kershner@unisys.com \
--cc=SParMaintainer@unisys.com \
--cc=Timothy.Sell@unisys.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robsonde@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 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).