From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH 0/6] V4L1 cleanups and videodev.h removal
Date: Mon, 27 Dec 2010 12:19:23 -0200 [thread overview]
Message-ID: <4D18A06B.6040902@redhat.com> (raw)
In-Reply-To: <201012271345.16124.hverkuil@xs4all.nl>
Em 27-12-2010 10:45, Hans Verkuil escreveu:
> On Monday, December 27, 2010 13:33:52 Mauro Carvalho Chehab wrote:
>> Em 27-12-2010 10:21, Hans Verkuil escreveu:
>>> On Monday, December 27, 2010 12:38:48 Mauro Carvalho Chehab wrote:
>>>> Now that all hard work to remove V4L1 happened, it doesn't make
>>>> sense on keeping videodev.h just because of two obsoleted drivers.
>>>
>>> Perhaps it is also time to mark the videodev2.h _OLD ioctls for removal in
>>> 2.6.39?
>>>
>>> If we are getting rid of old stuff anyway, then this will also be a nice
>>> cleanup.
>>>
>>> Perhaps we can even delete it without marking it for removal. After all,
>>> removing it will only affect binaries compiled against a *really* old kernel
>>> (I suspect 2.5.something). Anything that has been recompiled will automatically
>>> use the correct ioctls.
>>
>> We can't just remove the _OLD, as they're used internally, in order to handle
>> those old binaries. I think that not all come from 2.5 times. So, the better is to
>> mark them to be removed for .39.
>
> I double checked and they were introduced in 2.6.2 except for CROPCAP_OLD which
> was introduced in 2.6.6.
Thanks for the research.
>
> Do you want me to mark them for removal or will you?
I did it. Just sent to the ML. I'm basically with my hands tight, as kernel's Patchwork
is not working today, so I have some time to do some basic cleanup, while waiting for
someone to restart patchwork service.
Cheers,
Mauro
prev parent reply other threads:[~2010-12-27 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 11:38 [PATCH 0/6] V4L1 cleanups and videodev.h removal Mauro Carvalho Chehab
2010-12-27 12:21 ` Hans Verkuil
2010-12-27 12:33 ` Mauro Carvalho Chehab
2010-12-27 12:45 ` Hans Verkuil
2010-12-27 14:19 ` Mauro Carvalho Chehab [this message]
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=4D18A06B.6040902@redhat.com \
--to=mchehab@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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).