linux-kernel - Re: [PATCH 03/10] Intel PTI implementaiton of MIPI 1149.7.

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]

Date:	Mon, 28 Feb 2011 19:36:59 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	J Freyensee <james_p_freyensee@...ux.intel.com>
cc:	Arnd Bergmann <arnd@...db.de>, gregkh@...e.de,
	linux-kernel@...r.kernel.org, suhail.ahmed@...el.com,
	christophe.guerard@...el.com
Subject: Re: [PATCH 03/10] Intel PTI implementaiton of MIPI 1149.7.

On Mon, 28 Feb 2011, J Freyensee wrote:
> On Mon, 2011-02-28 at 10:28 +0100, Arnd Bergmann wrote:
> > > +static struct miscdevice pti_char_driver = {
> > > +	.minor		= MISC_DYNAMIC_MINOR,
> > > +	.name		= CHARNAME,
> > > +	.fops		= &pti_char_driver_ops
> > > +};
> > > +
> > 
> > It's really strange to have both a tty and a character device that have similar
> > operations. Why can't you have the pti_char_driver functionality in the tty driver?
> > 
> 
> Because that is not what the customer wanted and this is why the driver
> is located in misc/ ;-).  

Brilliant argument. Next time you tell us that the customer wanted a
root hole in his driver and that's why you put it there.

What's the fcking technical reason for having a char and a tty device ?

Thanks,

	tglx
--
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/