From: Sean Young <sean@mess.org>
To: Hans Petter Selasky <hps@selasky.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH] [MEDIA] Use standard integer types
Date: Tue, 21 Jul 2020 08:57:07 +0100 [thread overview]
Message-ID: <20200721075707.GA1497@gofer.mess.org> (raw)
In-Reply-To: <4c32e020-1da4-5fbd-a445-121d361bd1e0@selasky.org>
On Mon, Jul 20, 2020 at 08:10:18PM +0200, Hans Petter Selasky wrote:
> Fixes compilation under FreeBSD.
This looks good, but there are other places which uses the same types:
https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/keytable.c#n58
https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/keytable.c#n85
Do these not affect the build?
>
> Signed-off-by: Hans Petter Selasky <hps@selasky.org>
> ---
> utils/common/keymap.h | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/utils/common/keymap.h b/utils/common/keymap.h
> index 99833827..dc198bc1 100644
> --- a/utils/common/keymap.h
> +++ b/utils/common/keymap.h
> @@ -2,6 +2,8 @@
> #ifndef __KEYMAP_H
> #define __KEYMAP_H
Your patch got mangled, there two spaces before the # on these two lines.
Thanks
Sean
>
> +#include <stdint.h>
> +
> struct keymap {
> struct keymap *next;
> char *name;
> @@ -20,16 +22,16 @@ struct protocol_param {
>
> struct scancode_entry {
> struct scancode_entry *next;
> - u_int64_t scancode;
> + uint64_t scancode;
> char *keycode;
> };
>
> struct raw_entry {
> struct raw_entry *next;
> - u_int64_t scancode;
> - u_int32_t raw_length;
> + uint64_t scancode;
> + uint32_t raw_length;
> char *keycode;
> - u_int32_t raw[1];
> + uint32_t raw[1];
> };
>
> void free_keymap(struct keymap *map);
> --
> 2.27.0
next prev parent reply other threads:[~2020-07-21 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 18:10 [PATCH] [MEDIA] Use standard integer types Hans Petter Selasky
2020-07-21 7:57 ` Sean Young [this message]
2020-07-21 10:46 ` Hans Petter Selasky
2020-07-21 10:53 ` Hans Petter Selasky
2020-07-21 17:07 ` Sean Young
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=20200721075707.GA1497@gofer.mess.org \
--to=sean@mess.org \
--cc=hps@selasky.org \
--cc=linux-media@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