From: "Rémi Denis-Courmont" <remi@remlab.net>
To: "Rémi Denis-Courmont" <remi@remlab.net>
Cc: Sakari Ailus <sakari.ailus@iki.fi>,
Hans Verkuil <hverkuil@xs4all.nl>, <linux-media@vger.kernel.org>,
<laurent.pinchart@ideasonboard.com>, <mchehab@redhat.com>,
<nbowler@elliptictech.com>, <james.dutton@gmail.com>
Subject: Re: [RFC v3 1/2] v4l: Do not use enums in IOCTL structs
Date: Thu, 03 May 2012 12:58:57 +0200 [thread overview]
Message-ID: <3b9e7aa585169179c0140508e72cf97b@chewa.net> (raw)
In-Reply-To: <2ce6f5bbb2d0c3b1c7e9e77a2e4a89cf@chewa.net>
Answering myself.
On Thu, 03 May 2012 12:57:00 +0200, Rémi Denis-Courmont <remi@remlab.net>
wrote:
> On Thu, 3 May 2012 00:39:15 +0300, Sakari Ailus <sakari.ailus@iki.fi>
> wrote:
>> - ppc64: int is 64 bits there, and thus also enums,
>
> Really?
No, really not:
http://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi-1.9.html#FUND-TYPE
--
Rémi Denis-Courmont
Sent from my collocated server
next prev parent reply other threads:[~2012-05-03 10:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 19:13 [RFC v2 0/2] V4L2 IOCTL enum compat wrapper Sakari Ailus
2012-05-02 19:13 ` [RFC v3 1/2] v4l: Do not use enums in IOCTL structs Sakari Ailus
2012-05-02 20:45 ` Hans Verkuil
2012-05-02 21:39 ` Sakari Ailus
2012-05-03 7:02 ` Hans Verkuil
2012-05-03 13:42 ` Mauro Carvalho Chehab
2012-05-03 14:12 ` Hans Verkuil
2012-05-03 10:57 ` Rémi Denis-Courmont
2012-05-03 10:58 ` Rémi Denis-Courmont [this message]
2012-05-03 12:20 ` Sakari Ailus
2012-05-02 22:17 ` Mauro Carvalho Chehab
2012-05-03 0:42 ` Andy Walls
2012-05-03 10:22 ` Mauro Carvalho Chehab
2012-05-03 10:35 ` Sakari Ailus
2012-05-03 12:07 ` Mauro Carvalho Chehab
2012-05-03 10:45 ` Sylwester Nawrocki
2012-05-03 23:02 ` Andy Walls
2012-05-03 10:39 ` Mauro Carvalho Chehab
2012-05-02 19:13 ` [RFC v3 2/2] v4l: Implement compat functions for enum to __u32 change Sakari Ailus
2012-05-02 22:32 ` Mauro Carvalho Chehab
2012-05-02 23:38 ` Laurent Pinchart
2012-05-03 12:20 ` Mauro Carvalho Chehab
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=3b9e7aa585169179c0140508e72cf97b@chewa.net \
--to=remi@remlab.net \
--cc=hverkuil@xs4all.nl \
--cc=james.dutton@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=nbowler@elliptictech.com \
--cc=sakari.ailus@iki.fi \
/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.