Linux Documentation
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Haren Myneni <haren@linux.ibm.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Andrew Donnellan <ajd@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Akshay Gupta <akshay.gupta@amd.com>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	hans@jjverkuil.nl, laurent.pinchart@ideasonboard.com,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	Lee Jones <lee@kernel.org>
Subject: Re: [PATCH v2 0/3] Document Media Controller IOCTL number assignments
Date: Fri, 5 Sep 2025 14:02:51 +0300	[thread overview]
Message-ID: <aLrDWyxiiF2hPu_8@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <2025090509-stoppable-contrite-13ae@gregkh>

Hi Greg,

On Fri, Sep 05, 2025 at 12:32:45PM +0200, Greg Kroah-Hartman wrote:
> On Fri, Sep 05, 2025 at 01:25:33PM +0300, Sakari Ailus wrote:
> > Hi Jonathan, Greg, Miguel, others,
> > 
> > On Tue, May 27, 2025 at 08:56:45AM +0300, Sakari Ailus wrote:
> > > Hello all,
> > > 
> > > The Media Controller uses IOCTL numbers with '|' type up to 0x81 but the
> > > range from 0x80 upwards is documented to belong to samples. The samples,
> > > however, are currently using these values. Solve the problem by bumping
> > > the top of the MC range and the samples allocation by 0x10 as the samples
> > > don't require a stable IOCTL interface.
> > 
> > Could you comment on this, please?
> 
> Why not just live with the overlap?  What problem is this causing?  It's
> the MC subsystem's "bug" in that it took over an ioctl range that was
> already documented as being used by something else :)

I do agree ideally this shouldn't have happened in the first place, but I
think it's also cleaner if we can have separate ranges. Pushing samples out
a little doesn't look like an issue to me. The set also adds a comment on
not adding media IOCTLs beyond the new allocation.

-- 
Kind regards,

Sakari Ailus

      reply	other threads:[~2025-09-05 11:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27  5:56 [PATCH v2 0/3] Document Media Controller IOCTL number assignments Sakari Ailus
2025-05-27  5:56 ` [PATCH v2 1/3] Documentation: Bump media IOCTL reserved numbers Sakari Ailus
2025-05-27  5:56 ` [PATCH v2 2/3] media: uapi: Document IOCTL number assignment Sakari Ailus
2025-05-27  5:56 ` [PATCH v2 3/3] samples: rust_misc_device: Bump IOCTL numbers Sakari Ailus
2025-09-05 10:25 ` [PATCH v2 0/3] Document Media Controller IOCTL number assignments Sakari Ailus
2025-09-05 10:32   ` Greg Kroah-Hartman
2025-09-05 11:02     ` Sakari Ailus [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=aLrDWyxiiF2hPu_8@valkosipuli.retiisi.eu \
    --to=sakari.ailus@iki.fi \
    --cc=ajd@linux.ibm.com \
    --cc=akshay.gupta@amd.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hans@jjverkuil.nl \
    --cc=haren@linux.ibm.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lee@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=maddy@linux.ibm.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=mpe@ellerman.id.au \
    /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