All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@yandex.ru>
To: Arnd Bergmann <arnd@arndb.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Laurent Pinchart <laurentp@cse-semaphore.com>,
	linux-mtd@lists.infradead.org, v4l-dvb-maintainer@linuxtv.org
Subject: Re: UBI/DVB ioctl conflict?
Date: Mon, 08 Dec 2008 18:33:39 +0200	[thread overview]
Message-ID: <493D4C63.5040502@yandex.ru> (raw)
In-Reply-To: <200812081650.54346.arnd@arndb.de>

Arnd Bergmann wrote:
> On Monday 08 December 2008, Artem Bityutskiy wrote:
>> On Mon, 2008-12-08 at 10:41 +0100, Laurent Pinchart wrote:
>>> Correct me if I'm wrong, but doesn't this only matters for devices that would 
>>> implement both the UBI and DVB API on the same inode ? That would be quite 
>>> unlikely.
>> Yeah, I guess. But this anyway makes sense to keep ioctls
>> non-overlapping.
> 
> We try hard (but sometimes fail) to keep every ioctl number unique.
> The reason for this is that the device drivers are not the only
> pieces of code that look at them. Specifically, three other things
> frequently cause problems here:

Thanks for the reply. Do you know the status of the
Documentation/ioctl/ioctl-number.txt file - it does not seem to be up-to-date.
Should I document add UBI ioctls there?

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind@yandex.ru>
To: Arnd Bergmann <arnd@arndb.de>
Cc: dedekind@infradead.org,
	Laurent Pinchart <laurentp@cse-semaphore.com>,
	linux-mtd@lists.infradead.org,
	Josh Boyer <jwboyer@linux.vnet.ibm.com>,
	v4l-dvb-maintainer@linuxtv.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: UBI/DVB ioctl conflict?
Date: Mon, 08 Dec 2008 18:33:39 +0200	[thread overview]
Message-ID: <493D4C63.5040502@yandex.ru> (raw)
In-Reply-To: <200812081650.54346.arnd@arndb.de>

Arnd Bergmann wrote:
> On Monday 08 December 2008, Artem Bityutskiy wrote:
>> On Mon, 2008-12-08 at 10:41 +0100, Laurent Pinchart wrote:
>>> Correct me if I'm wrong, but doesn't this only matters for devices that would 
>>> implement both the UBI and DVB API on the same inode ? That would be quite 
>>> unlikely.
>> Yeah, I guess. But this anyway makes sense to keep ioctls
>> non-overlapping.
> 
> We try hard (but sometimes fail) to keep every ioctl number unique.
> The reason for this is that the device drivers are not the only
> pieces of code that look at them. Specifically, three other things
> frequently cause problems here:

Thanks for the reply. Do you know the status of the
Documentation/ioctl/ioctl-number.txt file - it does not seem to be up-to-date.
Should I document add UBI ioctls there?

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2008-12-08 16:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-07 14:58 UBI/DVB ioctl conflict? Josh Boyer
2008-12-08  6:20 ` Artem Bityutskiy
2008-12-08  6:20   ` Artem Bityutskiy
2008-12-08  9:41   ` Laurent Pinchart
2008-12-08  9:41     ` Laurent Pinchart
2008-12-08  9:51     ` Artem Bityutskiy
2008-12-08  9:51       ` Artem Bityutskiy
2008-12-08 15:50       ` Arnd Bergmann
2008-12-08 15:50         ` Arnd Bergmann
2008-12-08 16:33         ` Artem Bityutskiy [this message]
2008-12-08 16:33           ` Artem Bityutskiy
2008-12-08 20:30           ` Arnd Bergmann
2008-12-08 20:30             ` Arnd Bergmann
2008-12-08 13:31     ` Jamie Lokier
2008-12-08 13:31       ` Jamie Lokier

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=493D4C63.5040502@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=arnd@arndb.de \
    --cc=laurentp@cse-semaphore.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=v4l-dvb-maintainer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.