From: Christoph Hellwig <hch@lst.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-acpi@vger.kernel.org, devel@linuxdriverproject.org,
sparmaintainer@unisys.com, devel@driverdev.osuosl.org,
linux-wireless@vger.kernel.org, linux-watchdog@vger.kernel.org,
linux-efi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, Lukas Wunner <lukas@wunner.de>
Subject: Re: [PATCH v1 5/6] uuid: Kill uapi/uuid.h
Date: Mon, 24 Jul 2017 17:54:41 +0200 [thread overview]
Message-ID: <20170724155441.GC17917@lst.de> (raw)
In-Reply-To: <20170719182857.73693-6-andriy.shevchenko@linux.intel.com>
> diff --git a/scripts/mod/file2alias.c b/scripts/mod/file2alias.c
> index 29d6699d5a06..1c68709123aa 100644
> --- a/scripts/mod/file2alias.c
> +++ b/scripts/mod/file2alias.c
> @@ -36,7 +36,7 @@ typedef uint16_t __u16;
> typedef unsigned char __u8;
> typedef struct {
> __u8 b[16];
> -} uuid_le;
> +} guid_t;
>
> /* Big exception to the "don't include kernel headers into userspace, which
> * even potentially has different endianness and word sizes, since
> @@ -134,7 +134,7 @@ static inline void add_wildcard(char *str)
> strcat(str + len, "*");
> }
>
> -static inline void add_uuid(char *str, uuid_le uuid)
> +static inline void add_uuid(char *str, guid_t uuid)
> {
> int len = strlen(str);
This should probably be split into a separate patch.
next prev parent reply other threads:[~2017-07-24 15:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 18:28 [PATCH v1 0/6] uuid: Convert rest users to new API Andy Shevchenko
2017-07-19 18:28 ` [PATCH v1 1/6] efi: Switch to use new generic UUID API Andy Shevchenko
2017-07-20 12:18 ` Ard Biesheuvel
2017-07-25 10:40 ` Andy Shevchenko
2017-07-26 7:52 ` Christoph Hellwig
2017-07-26 8:36 ` Ard Biesheuvel
2017-08-30 12:41 ` Christoph Hellwig
2017-07-19 18:28 ` [PATCH v1 2/6] mei: " Andy Shevchenko
2017-07-22 18:45 ` kbuild test robot
2017-07-19 18:28 ` [PATCH v1 3/6] staging: unisys: " Andy Shevchenko
2017-07-26 10:01 ` Andy Shevchenko
2017-07-30 15:32 ` Greg Kroah-Hartman
2017-07-30 17:26 ` Andy Shevchenko
2017-07-30 17:37 ` Greg Kroah-Hartman
2017-07-31 17:20 ` Andy Shevchenko
2017-08-30 12:38 ` Christoph Hellwig
2017-08-30 13:09 ` Andy Shevchenko
2017-08-30 13:11 ` Greg Kroah-Hartman
2017-07-19 18:28 ` [PATCH v1 4/6] vmbus: " Andy Shevchenko
2017-07-19 20:18 ` Haiyang Zhang
2017-07-19 21:54 ` Andy Shevchenko
2017-07-22 18:46 ` kbuild test robot
2017-07-24 15:54 ` Christoph Hellwig
2017-07-19 18:28 ` [PATCH v1 5/6] uuid: Kill uapi/uuid.h Andy Shevchenko
2017-07-22 18:48 ` kbuild test robot
2017-07-24 15:54 ` Christoph Hellwig [this message]
2017-07-19 18:28 ` [PATCH v1 6/6] device property: Switch to use new generic UUID API Andy Shevchenko
2017-07-19 19:27 ` Rafael J. Wysocki
2017-07-25 14:12 ` Mika Westerberg
2017-07-26 0:21 ` Rafael J. Wysocki
2017-07-26 0:35 ` Andy Shevchenko
2017-07-26 0:27 ` Rafael J. Wysocki
2017-07-26 10:03 ` Andy Shevchenko
2017-07-26 18:58 ` Rafael J. Wysocki
2017-08-30 12:41 ` Christoph Hellwig
2017-08-30 13:46 ` Rafael J. Wysocki
2017-08-30 13:57 ` Christoph Hellwig
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=20170724155441.GC17917@lst.de \
--to=hch@lst.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sparmaintainer@unisys.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).