public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: "Savoy, Pavan" <pavan_savoy@ti.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: patch "Staging: ti-st: update ABI and TODO" added to staging-next tree
Date: Thu, 29 Jul 2010 07:53:02 -0700	[thread overview]
Message-ID: <20100729145302.GB20709@suse.de> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E7394044EE51EF4@dbde02.ent.ti.com>

On Thu, Jul 29, 2010 at 12:49:59PM +0530, Savoy, Pavan wrote:
> Greg,
> 
>  
> > -----Original Message-----
> > From: gregkh@suse.de [mailto:gregkh@suse.de]
> > Sent: Wednesday, July 28, 2010 10:24 AM
> > To: Savoy, Pavan; gregkh@suse.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

  reply	other threads:[~2010-07-29 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12803306292159@site>
2010-07-29  7:19 ` patch "Staging: ti-st: update ABI and TODO" added to staging-next tree Savoy, Pavan
2010-07-29 14:53   ` Greg KH [this message]
2010-07-29 15:18     ` Alan Cox
2010-07-30  5:30     ` Savoy, Pavan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100729145302.GB20709@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavan_savoy@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox