linux-kernel - Re: [PATCH 00/70] tty updates proposed for 2.6.27

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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 21 Jun 2008 15:23:44 +0200
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Greg KH <greg@...ah.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/70] tty updates proposed for 2.6.27

Hi Greg,

> > This patch series introduces the idea of a tty_port - a common structure
> > that eventually all ports will have. Some drivers are migrated to make partial
> > use of the tty port commonality and helpers but only a little.
> > 
> > On the USB side the USB tty API is changed to fix a whole pile of races where
> > tty->port->tty cannot be assumed to be tty (because of hangup/reopen). The
> > USB drivers all get a spring clean and the entire pile have been dragged into
> > CodingStyle near compliance (some cases where the checkpatch whines that
> > make no sense have been ignored).
> > 
> > Greg: At the end of this series there shouldn't be any white space issues
> > although some earlier patches introduce them and later ones take them away
> 
> Ah, thanks for resending these, as they are primarily USB changes, any
> objection for me to take these through my USB tree?

for everything that Alan touches in the Bluetooth drivers, you have an
ack from me. I am happy if this goes in quickly and I only have to
re-base my tree once.

Regards

Marcel


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