linux-kernel - Re: patch "Staging: ti-st: update ABI and TODO" added to staging-next tree

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: <20100729145302.GB20709@suse.de>
Date:	Thu, 29 Jul 2010 07:53:02 -0700
From:	Greg KH <gregkh@...e.de>
To:	"Savoy, Pavan" <pavan_savoy@...com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: patch "Staging: ti-st: update ABI and TODO" added to
	staging-next tree

On Thu, Jul 29, 2010 at 12:49:59PM +0530, Savoy, Pavan wrote:
> Greg,
> 
>  
> > -----Original Message-----
> > From: gregkh@...e.de [mailto:gregkh@...e.de]
> > Sent: Wednesday, July 28, 2010 10:24 AM
> > To: Savoy, Pavan; gregkh@...e.de
> > Subject: patch "Staging: ti-st: update ABI and TODO" added to staging-next tree
> 
> Is it good enough to be moved out of staging?

I don't know, I haven't reviewed it.  Do you want me to do so?  It looks
like you still have a number of things on your TODO list, why not
resolve those first?

> I mean the multi-device thingy would be more or less a nice to have
> feature than being a bug, isn't it?

I don't think Alan thinks so.

> The ease for me would be once out of staging, I can cleanup the
> platform device mess too, since our L-O tree needs to be have some
> patches in the arch/arm/board-XX.c sort of files...

Promises to clean up code after it leaves staging is generally not a
good idea :)

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/