linux-kernel - Re: UBI/DVB ioctl conflict?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200812082130.14420.arnd@arndb.de>
Date:	Mon, 8 Dec 2008 21:30:13 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Artem Bityutskiy <dedekind@...dex.ru>
Cc:	dedekind@...radead.org,
	Laurent Pinchart <laurentp@...-semaphore.com>,
	linux-mtd@...ts.infradead.org,
	Josh Boyer <jwboyer@...ux.vnet.ibm.com>,
	v4l-dvb-maintainer@...uxtv.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: UBI/DVB ioctl conflict?

On Monday 08 December 2008, Artem Bityutskiy wrote:
> Arnd Bergmann wrote:
> > 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?

Yes, please. The best we can do is if everyone documents his own stuff.

	Arnd <><
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/