From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Andreas Oberritter <obi@linuxtv.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org,
Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [RFCv2 PATCH 12/12] Remove audio.h, video.h and osd.h.
Date: Thu, 24 Nov 2011 15:58:38 -0200 [thread overview]
Message-ID: <4ECE85CE.7040807@redhat.com> (raw)
In-Reply-To: <4ECE8434.5060106@linuxtv.org>
Em 24-11-2011 15:51, Andreas Oberritter escreveu:
> On 24.11.2011 18:44, Hans Verkuil wrote:
>> On Thursday, November 24, 2011 18:08:05 Andreas Oberritter wrote:
>>> Don't break existing Userspace APIs for no reason! It's OK to add the
>>> new API, but - pretty please - don't just blindly remove audio.h and
>>> video.h. They are in use since many years by av7110, out-of-tree drivers
>>> *and more importantly* by applications. Yes, I know, you'd like to see
>>> those out-of-tree drivers merged, but it isn't possible for many
>>> reasons. And even if they were merged, you'd say "Port them and your
>>> apps to V4L". No! That's not an option.
>>
>> I'm not breaking anything. All apps will still work.
>>
>> One option (and it depends on whether people like it or not) is to have
>> audio.h, video.h and osd.h just include av7110.h and add a #warning
>> that these headers need to be replaced by the new av7110.h.
>>
>> And really remove them at some point in the future.
>>
>> But the important thing to realize is that the ABI hasn't changed (unless
>> I made a mistake somewhere).
>
> So why don't you just leave the headers where they are and add a notice
> about the new V4L API as a comment?
>
> What you proposed breaks compilation. If you add a warning, it breaks
> compilation for programs compiled with -Werror. Both are regressions.
I don't mind doing it for 3.3 kernel, and add a note at
Documentation/feature-removal-schedule.txt that the
headers will go away on 3.4. This should give distributions
and app developers enough time to prevent build failures, and
prepare for the upcoming changes.
Regards,
Mauro.
>
> Regards,
> Andreas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-24 17:58 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 13:38 Remove audio and video DVBv5 API Hans Verkuil
2011-11-24 13:38 ` [RFCv2 PATCH 01/12] v4l2: add VIDIOC_(TRY_)DECODER_CMD Hans Verkuil
2011-11-24 13:38 ` [RFCv2 PATCH 02/12] v4l spec: document VIDIOC_(TRY_)DECODER_CMD Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 03/12] ivtv: implement new decoder command ioctls Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 04/12] v4l2-ctrls: add new controls for MPEG decoder devices Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 05/12] Document decoder controls Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 06/12] ivtv: implement new " Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 07/12] cx18/ddbridge: remove unused headers Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 08/12] ivtv: extend ivtv.h with structs and ioctls from dvb/audio.h and video.h Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 09/12] ivtv: use the new ivtv-specific ioctls from ivtv.h Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 10/12] av7110: replace audio.h, video.h and osd.h by av7110.h Hans Verkuil
2011-11-24 23:24 ` Oliver Endriss
2011-11-25 15:35 ` Klaus Schmidinger
2011-11-24 13:39 ` [RFCv2 PATCH 11/12] Replace audio.xml and video.xml with av.xml Hans Verkuil
2011-11-24 13:39 ` [RFCv2 PATCH 12/12] Remove audio.h, video.h and osd.h Hans Verkuil
2011-11-24 17:08 ` Andreas Oberritter
2011-11-24 17:37 ` Mauro Carvalho Chehab
2011-11-24 17:59 ` Manu Abraham
2011-11-24 18:01 ` Andreas Oberritter
2011-11-24 23:32 ` Oliver Endriss
2011-11-24 17:44 ` Hans Verkuil
2011-11-24 17:51 ` Andreas Oberritter
2011-11-24 17:58 ` Mauro Carvalho Chehab [this message]
2011-11-24 18:07 ` Andreas Oberritter
2011-11-24 18:25 ` Mauro Carvalho Chehab
2011-11-24 18:34 ` Manu Abraham
2011-11-25 1:09 ` Andreas Oberritter
2011-11-25 2:44 ` Mauro Carvalho Chehab
2011-11-25 12:55 ` Andreas Oberritter
2011-11-25 15:18 ` Mauro Carvalho Chehab
2011-11-25 15:25 ` Hans Verkuil
2011-11-25 16:00 ` Mauro Carvalho Chehab
2011-11-24 18:01 ` Manu Abraham
2011-11-24 18:08 ` Mauro Carvalho Chehab
2011-11-24 18:13 ` Manu Abraham
2011-11-24 18:47 ` Mauro Carvalho Chehab
2011-11-24 18:51 ` Manu Abraham
2011-11-24 19:05 ` Manu Abraham
2011-11-25 12:00 ` Andreas Oberritter
2011-11-25 13:48 ` Mauro Carvalho Chehab
2011-11-25 13:59 ` Manu Abraham
2011-11-25 14:41 ` Andreas Oberritter
2011-11-25 15:38 ` Mauro Carvalho Chehab
2011-11-25 16:03 ` Andreas Oberritter
2011-11-25 16:26 ` Mauro Carvalho Chehab
2011-11-25 16:51 ` Manu Abraham
2011-11-25 22:06 ` Andreas Oberritter
2011-11-26 5:55 ` Oliver Endriss
2011-11-26 6:25 ` Manu Abraham
2011-11-26 11:32 ` Mauro Carvalho Chehab
2011-11-26 11:59 ` Mauro Carvalho Chehab
2011-11-26 12:46 ` Oliver Endriss
2011-11-26 11:49 ` Hans Verkuil
2011-11-26 20:27 ` Andreas Oberritter
2011-11-27 18:28 ` Mauro Carvalho Chehab
2011-11-26 21:58 ` Manu Abraham
2011-11-27 19:03 ` Mauro Carvalho Chehab
2011-11-27 19:27 ` Manu Abraham
2011-11-27 21:39 ` Mauro Carvalho Chehab
2011-11-27 22:24 ` Manu Abraham
2011-11-27 22:50 ` Mauro Carvalho Chehab
2011-11-26 22:11 ` Manu Abraham
2011-11-25 15:22 ` Hans Verkuil
2011-11-25 15:52 ` Mauro Carvalho Chehab
2011-11-26 10:44 ` Hans Verkuil
2011-11-25 15:58 ` Manu Abraham
2011-11-25 16:03 ` Mauro Carvalho Chehab
2011-11-25 16:11 ` Manu Abraham
2011-11-24 23:25 ` Oliver Endriss
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=4ECE85CE.7040807@redhat.com \
--to=mchehab@redhat.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=obi@linuxtv.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;
as well as URLs for NNTP newsgroup(s).