public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: dhowells@redhat.com, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [GIT PULL] Disintegrate UAPI for media
Date: Wed, 10 Oct 2012 12:26:27 +0100	[thread overview]
Message-ID: <5255.1349868387@warthog.procyon.org.uk> (raw)
In-Reply-To: <20121009183908.1e402a43@infradead.org>

Mauro Carvalho Chehab <mchehab@infradead.org> wrote:

> 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).

As long as they're relying on the -I flags provided by the build tree, that
oughtn't to be a problem.  If they're doing their own -I flags, they'll need
to add -I include/uapi too (_after_ -I include).

> 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).

Do you want me to do anything?  I should be able to incorporate a patch prior
to the disintegration of linux/dvb/ if you have one.

David

  reply	other threads:[~2012-10-10 11:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 13:30 [GIT PULL] Disintegrate UAPI for media David Howells
2012-10-09 21:39 ` Mauro Carvalho Chehab
2012-10-10 11:26   ` David Howells [this message]
2012-10-11  8:23   ` Oliver Endriss
2012-10-11  8:41     ` Manu Abraham
2012-10-11 12:37     ` Mauro Carvalho Chehab
2012-10-11 14:05       ` David Howells
2012-10-11 14:57         ` 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=5255.1349868387@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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