From: Arnd Bergmann <arnd@arndb.de>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-api@vger.kernel.org,
Javier Martinez Canillas <javier@osg.samsung.com>
Subject: Re: [PATCH] [media] uapi/media.h: Use u32 for the number of graph objects
Date: Thu, 17 Dec 2015 14:55:11 +0100 [thread overview]
Message-ID: <2035986.3qXU4Qokl3@wuerfel> (raw)
In-Reply-To: <20151217104556.70d4f0f8@recife.lan>
On Thursday 17 December 2015 10:45:56 Mauro Carvalho Chehab wrote:
> If I understood well, he's proposing to do is:
>
> struct media_v2_topology {
> __u64 topology_version;
>
> __u32 num_entities;
> __u32 num_interfaces;
> __u32 num_pads;
> __u32 num_links;
>
> __u64 ptr_entities;
> __u64 ptr_interfaces;
> __u64 ptr_pads;
> __u64 ptr_links;
> };
>
> The problem is that, if we latter need to extend it to add a new type
> the extension will not be too nice. For example, I did some experimental
> patches adding graph groups:
>
Can you clarify how the 'topology_version' is used here? Is that
the version of the structure layout that decides how we interpret the
rest, or is it a number that is runtime dependent?
If this is an API version, I think the answer can simply be to drop
the topology_version field entirely, and use a new ioctl command code
whenever the API changes. This is the preferred method anyway.
Arnd
next prev parent reply other threads:[~2015-12-17 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 11:09 [PATCH] [media] uapi/media.h: Use u32 for the number of graph objects Mauro Carvalho Chehab
[not found] ` <5672A69F.7020505@xs4all.nl>
2015-12-17 12:45 ` Mauro Carvalho Chehab
2015-12-17 13:55 ` Arnd Bergmann [this message]
2015-12-17 14:58 ` Mauro Carvalho Chehab
2015-12-17 15:20 ` Arnd Bergmann
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=2035986.3qXU4Qokl3@wuerfel \
--to=arnd@arndb.de \
--cc=hverkuil@xs4all.nl \
--cc=javier@osg.samsung.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@osg.samsung.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