LKML Archive on
help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <>
To: Linus Torvalds <>
Cc: Soeren Moch <>,
	Linux Media Mailing List <>,
	"" <>
Subject: Re: [Regression 5.14] media: dvb userspace api
Date: Tue, 24 Aug 2021 09:47:54 +0200	[thread overview]
Message-ID: <20210824094754.32ad5eab@coco.lan> (raw)
In-Reply-To: <>

Em Mon, 23 Aug 2021 09:58:00 -0700
Linus Torvalds <> escreveu:

> On Mon, Aug 23, 2021 at 7:59 AM Soeren Moch <> wrote:
> >
> > Linus,
> >
> > Is what I described directly above the new linux maintenance policy?  Or
> > is linux media a private kingdom where the community should keep away?
> > Is this a place where the subsystem maintainer is on a mission to
> > destroy everything instead of maintaining and improving it? Please tell
> > me what I understood wrong here.  
> So technically, the regression policy for the kernel is purely about
> the ABI - the _binary_ interface. That seems to not have broken - old
> programs continue to work.
> We very much try to discourage user space applications from using the
> kernel header files directly - even projects like glibc etc are
> supposed to _copy_ them, not include the kernel headers.

Unfortunately, media APIs aren't part of projects like glibc. Almost all
open source media apps keep their own copies of the uAPI header files.

As far as I'm aware, the "full-feat" API is implemented only by some
modules of VDR. I don't know any other open source application using
such headers.

> Exactly because re-organization and changes to the kernel tree
> shouldn't be something that then causes random problems elsewhere that
> are so hard to test - and synchronize - from the kernel standpoint (or
> from the standpoint of the other end).
> That clearly doesn't seem to be the case in this situation. Which is
> annoying as heck.
> Mauro: there clearly _are_ users of those header files, and even
> apparently that one old driver out there. And those headers were in
> the 'uapi' directory, so while it is annoying how user space programs
> used them this way, I think it's also not entirely unreasonable.
> I have reverted the header file move. But I would also heartily
> recommend that whatever user program includes those headers (VDR -
> anything else?) should take snapshots of these specific kernel
> headers.
> I'm not convinced that it makes sense to move the av7110 driver back
> from staging - it may continue to work, but it _is_ old and there is
> no maintenance - and I would certainly suggest that any other
> out-of-tree driver that uses these old interfaces that nothing else
> implements shouldn't do so, considering that nothing else implements
> them.
> So the only thing I did was move the header files back, and mark that
> move to be backported to 5.13 stable.



  parent reply	other threads:[~2021-08-24  7:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 12:15 Soeren Moch
2021-08-19 11:31 ` Mauro Carvalho Chehab
2021-08-21 13:58   ` Manu Abraham
2021-08-22 15:21   ` Soeren Moch
2021-08-22 17:47     ` Mauro Carvalho Chehab
2021-08-23 14:59       ` Soeren Moch
2021-08-23 16:58         ` Linus Torvalds
2021-08-23 20:16           ` Soeren Moch
2021-08-24  7:47           ` Mauro Carvalho Chehab [this message]
2021-08-24 20:01             ` Honza P
2021-08-25  2:55           ` Manu Abraham
2021-08-25  6:33             ` Mauro Carvalho Chehab
2021-08-25 16:16               ` Manu Abraham
2021-08-26 12:26                 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210824094754.32ad5eab@coco.lan \ \ \ \ \ \
    --subject='Re: [Regression 5.14] media: dvb userspace api' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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