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] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E7E187B.4060507@gmail.com>
Date:	Sat, 24 Sep 2011 19:50:51 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Greg KH <gregkh@...e.de>
CC:	Jiri Slaby <jslaby@...e.cz>, Greg KH <greg@...ah.com>,
	Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@...esas.com>,
	linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 1/4] TTY: serial, fix locking imbalance

On 09/24/2011 12:04 AM, Greg KH wrote:
> On Fri, Sep 23, 2011 at 09:21:20PM +0200, Jiri Slaby wrote:
>> But if there are more trees depending on the tree, then OK, I will live
>> with that ;).
> 
> For the tty tree, I really doubt it, but I am not sure (rumor has it
> that some people are basing on it, but that might just be rumor.)

Ok, for the other uart patches I have, it would be convenient for me to
have the possibility of rebase. Would you mind if I add something like
uart-cleanup tree to the -next tree and will have the patches there
until I send them to you?

Just for the purpose of fine tuning (and rebasing) if something needs to
be fixed in them. The code is so complex, that I'm afraid I omitted some
semi-hidden dependency. And it would be great to fix patches like when I
used to work with the -mm tree.

thanks,
-- 
js
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ