From: "Kershner, David A" <David.Kershner@unisys.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: *S-Par-Maintainer <SParMaintainer@unisys.com>
Subject: RE: [PATCH v2] staging: unisys: Switch to use new generic UUID API
Date: Tue, 1 Aug 2017 19:08:11 +0000 [thread overview]
Message-ID: <CY4PR07MB3176B2BCF3DA617DD17DF247F0B30@CY4PR07MB3176.namprd07.prod.outlook.com> (raw)
In-Reply-To: <20170731171846.81384-1-andriy.shevchenko@linux.intel.com>
> -----Original Message-----
> From: Andy Shevchenko [mailto:andriy.shevchenko@linux.intel.com]
> Sent: Monday, July 31, 2017 1:19 PM
> Subject: [PATCH v2] staging: unisys: Switch to use new generic UUID API
>
> There are new types and helpers that are supposed to be used in new code.
>
> As a preparation to get rid of legacy types and API functions do
> the conversion here.
>
> While here, re-indent couple of lines to increase readability.
>
> Cc: David Kershner <david.kershner@unisys.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: sparmaintainer@unisys.com
> Cc: devel@driverdev.osuosl.org
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Acked-by: David Kershner <david.kershner@unisys.com>
> ---
> drivers/staging/unisys/Documentation/overview.txt | 14 +++----
> drivers/staging/unisys/include/channel.h | 29 ++++++--------
> drivers/staging/unisys/include/iochannel.h | 2 +-
> drivers/staging/unisys/include/visorbus.h | 14 +++----
> drivers/staging/unisys/visorbus/controlvmchannel.h | 16 ++++----
> drivers/staging/unisys/visorbus/vbuschannel.h | 8 ++--
> drivers/staging/unisys/visorbus/visorbus_main.c | 44 ++++++++++----------
> -
> drivers/staging/unisys/visorbus/visorbus_private.h | 6 +--
> drivers/staging/unisys/visorbus/visorchannel.c | 46 +++++++++++----------
> -
> drivers/staging/unisys/visorbus/visorchipset.c | 33 +++++++++-------
> drivers/staging/unisys/visorhba/visorhba_main.c | 6 +--
> drivers/staging/unisys/visorinput/visorinput.c | 38 +++++++++---------
> drivers/staging/unisys/visornic/visornic_main.c | 6 +--
> 13 files changed, 130 insertions(+), 132 deletions(-)
prev parent reply other threads:[~2017-08-01 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 17:18 Andy Shevchenko
2017-08-01 19:08 ` Kershner, David A [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=CY4PR07MB3176B2BCF3DA617DD17DF247F0B30@CY4PR07MB3176.namprd07.prod.outlook.com \
--to=david.kershner@unisys.com \
--cc=SParMaintainer@unisys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®