linux-kernel - Re: [PATCH 0/3] Fix the TIOCGICOUNT problem for good

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: <20100916230157.0c045cdd@lxorguk.ukuu.org.uk>
Date:	Thu, 16 Sep 2010 23:01:57 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Greg KH <greg@...ah.com>
Cc:	Alan Cox <alan@...ux.intel.com>, linux-serial@...r.kernel.org,
	linux-kernel@...r.kernel.org, drosenberg@...curity.com
Subject: Re: [PATCH 0/3] Fix the TIOCGICOUNT problem for good

On Thu, 16 Sep 2010 11:44:46 -0700
Greg KH <greg@...ah.com> wrote:

> On Thu, Sep 16, 2010 at 06:21:06PM +0100, Alan Cox wrote:
> > Remembering to clear fields is something driver authors are simply never
> > going to remember to get right every new driver. Instead take the problem
> > away from them and give them a simple interface to do the job.
> 
> Looks good.  But is it ok if I keep the one driver patch I have now for
> .36 and queue this up for .37?  I'll handle the merge conflicts myself.

Probably sensible given the closeness of .36 and the scale of changes
--
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/