linux-kernel - Re: [PATCH] tty: Fix ptmx open without closed slave.

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]

Date:	Tue, 15 Jan 2013 23:56:17 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Ilya Zykov <ilya@...x.ru>
Cc:	Alan Cox <alan@...ux.intel.com>, Jiri Slaby <jslaby@...e.cz>,
	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [PATCH] tty: Fix ptmx open without closed slave.

On Wed, Jan 16, 2013 at 11:48:38AM +0400, Ilya Zykov wrote:
> 
> > 
> > Ok, I have a ton of patches from you, lots of different threads, patches
> > with the same subject, and I don't know what one Alan agreed to.
> > 
> > So, can you please resend what Alan and you agree should be applied to
> > the tree?
> > 
> 
> 
> I think only two important:
> [PATCH v4] tty: Add driver unthrottle in ioctl(...,TCFLSH,..).
> 
> [PATCH] tty: Correct tty buffer flush.
> With Alan's ACK from 04.12.2012 for kernel <= 3.7
> 
> But for kernel 3.8 I resent this 05.12.2012
> [PATCH -next 0/2] tty: Correct tty buffer flush.
> [PATCH -next 1/2] tty: Correct tty buffer flush.
> [PATCH -next 2/2] tty: Correct tty buffer flush.
> The last I resent with new description after Jiri's remark.

How can you have more than one patch with the same subject?  Please
resend all patches that you wish to see applied, with proper Subject:
lines and acks, if you have gotten them.

thanks,

greg k-h
--
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/