From: David Woodhouse <dwmw2@infradead.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
Brandon Philips <bphilips@suse.de>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Bastien Nocera <bnocera@redhat.com>
Subject: Re: v4l regression: V4L2_CID_[VH]CENTER disappeared without notice.
Date: Mon, 02 Jun 2008 20:59:38 +0100 [thread overview]
Message-ID: <1212436778.8810.27.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20080602201911.1a48cc83@core>
On Mon, 2008-06-02 at 20:19 +0100, Alan Cox wrote:
> > Don't forget to document how people are _supposed_ to use the v4l api
> > from userspace, though.
>
> Correct but those methods are not part of the V4L2 API and have not been
> for some considerable time.
It seems that message hadn't got through. Any suggestions as to how we
could make sure it does in future?
The usual answers are (in order of preference):
1) don't remove userspace APIs
2) don't remove userspace APIs
3) Documentation/feature-removal-schedule.txt
4) don't remove userspace APIs
It would be good if we could combine #3 with some form of
__deprecated... can we make that work for ioctls in userspace?
--
dwmw2
next prev parent reply other threads:[~2008-06-02 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804241931.m3OJVQiR022368@hera.kernel.org>
2008-06-02 15:46 ` v4l regression: V4L2_CID_[VH]CENTER disappeared without notice David Woodhouse
2008-06-02 15:56 ` Alan Cox
2008-06-02 18:10 ` Brandon Philips
2008-06-02 18:34 ` Mauro Carvalho Chehab
2008-06-02 19:24 ` David Woodhouse
2008-06-02 19:19 ` Alan Cox
2008-06-02 19:59 ` David Woodhouse [this message]
2008-06-02 19:45 ` Alan Cox
2008-06-02 21:13 ` 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=1212436778.8810.27.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bnocera@redhat.com \
--cc=bphilips@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=torvalds@linux-foundation.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