linux-kernel - Re: [GIT PULL] Disintegrate UAPI for media

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 9 Oct 2012 18:39:08 -0300
From:	Mauro Carvalho Chehab <mchehab@...radead.org>
To:	David Howells <dhowells@...hat.com>
Cc:	linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
	Hans Verkuil <hverkuil@...all.nl>
Subject: Re: [GIT PULL] Disintegrate UAPI for media

Em Tue, 09 Oct 2012 14:30:24 +0100
David Howells <dhowells@...hat.com> escreveu:

> Can you merge the following branch into the media tree please.
> 
> This is to complete part of the Userspace API (UAPI) disintegration for which
> the preparatory patches were pulled recently.  After these patches, userspace
> headers will be segregated into:
> 
> 	include/uapi/linux/.../foo.h
> 
> for the userspace interface stuff, and:
> 
> 	include/linux/.../foo.h
> 
> for the strictly kernel internal stuff.
> 
> ---
> The following changes since commit 9e2d8656f5e8aa214e66b462680cf86b210b74a8:
> 
>   Merge branch 'akpm' (Andrew's patch-bomb) (2012-10-09 16:23:15 +0900)
> 
> are available in the git repository at:
> 
> 
>   git://git.infradead.org/users/dhowells/linux-headers.git tags/disintegrate-media-20121009
> 
> for you to fetch changes up to 1c436decd49665be131887b08d172a7989cdceee:
> 
>   UAPI: (Scripted) Disintegrate include/linux/dvb (2012-10-09 09:48:42 +0100)
> 
> ----------------------------------------------------------------
> UAPI Disintegration 2012-10-09
> 
> ----------------------------------------------------------------
> David Howells (1):
>       UAPI: (Scripted) Disintegrate include/linux/dvb
> 
>  include/linux/dvb/Kbuild                |   8 -
>  include/linux/dvb/dmx.h                 | 130 +--------------
>  include/linux/dvb/video.h               | 249 +----------------------------
>  include/uapi/linux/dvb/Kbuild           |   8 +
>  include/{ => uapi}/linux/dvb/audio.h    |   0
>  include/{ => uapi}/linux/dvb/ca.h       |   0
>  include/uapi/linux/dvb/dmx.h            | 155 ++++++++++++++++++
>  include/{ => uapi}/linux/dvb/frontend.h |   0
>  include/{ => uapi}/linux/dvb/net.h      |   0
>  include/{ => uapi}/linux/dvb/osd.h      |   0
>  include/{ => uapi}/linux/dvb/version.h  |   0
>  include/uapi/linux/dvb/video.h          | 274 ++++++++++++++++++++++++++++++++
>  12 files changed, 439 insertions(+), 385 deletions(-)
>  rename include/{ => uapi}/linux/dvb/audio.h (100%)
>  rename include/{ => uapi}/linux/dvb/ca.h (100%)
>  create mode 100644 include/uapi/linux/dvb/dmx.h
>  rename include/{ => uapi}/linux/dvb/frontend.h (100%)
>  rename include/{ => uapi}/linux/dvb/net.h (100%)
>  rename include/{ => uapi}/linux/dvb/osd.h (100%)
>  rename include/{ => uapi}/linux/dvb/version.h (100%)
>  create mode 100644 include/uapi/linux/dvb/video.h

Hmm... last year, it was decided that we would be putting the DVB av7110-only
API files on a separate place, as the API there conflicts with V4L/alsa APIs
and are used only by one upstream driver (there were two drivers using them,
at that time). As you might notice, av7110 hardware is really old, not 
manufactured anymore since maybe 10 years ago, and it is an unmaintained
driver.

Some developers complained, arguing that moving it to a separate file would
be breaking the compilation on existing tools (they're basically concerned with
it due to out-of-tree drivers - mostly propietary ones, that use this API).

Now that we're moving everything, it does make sense to do that, moving 
dvb/(audio|osd|video).h to someplace else (maybe linux/dvb/av7110.h or
linux/dvb/legacy/*.h).

Regards,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/