public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Huewe <PeterHuewe@gmx.de>
To: devel@driverdev.osuosl.org
Cc: Greg KH <greg@kroah.com>, Willy Tarreau <w@1wt.eu>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: Staging tree status for the .32 kernel merge
Date: Thu, 10 Sep 2009 23:57:27 +0200	[thread overview]
Message-ID: <200909102357.27867.PeterHuewe@gmx.de> (raw)
In-Reply-To: <20090905145035.GA20698@kroah.com>

Am Saturday 05 September 2009 16:50:35 schrieb Greg KH:
> On Sat, Sep 05, 2009 at 02:39:51PM +0200, Willy Tarreau wrote:
> > Hi Greg,
> >
> > On Wed, Sep 02, 2009 at 09:14:30PM -0700, Greg KH wrote:
> > > 	- panel.  Another one that should be simple to merge.  Anyone?
> >
> > I just got an email from a guy who proposed to work on it and who
> > showed me he's currently running tests and fixing a bug when removing
> > the module.
> >
> > Hopefully he'll make enough progress to get the driver merged.
> >
> > This proves that the principle of the staging tree seems to work,
> > and that your call was useful ;-)
>
> Glad to hear it!

yeah - Greg's call definitely was useful!
Although I'm still not sure if there is a point to getting the driver merged 
or not -- see discussion: "staging panel driver"
http://driverdev.linuxdriverproject.org/pipermail/devel/2009-September/001610.html

More opinions/suggestions are welcomed - especially from people who are more 
into lcdproc than I am.

However I'm currently working on it anyways - I already eliminated the bug:
while removing the module misc_deregister gets called twice (keypad and led - 
both twice) - once in the  panel_detach function and once in the 
panel_cleanup_module function.

And of course the second call fails :)
I will provide a (very simple :) patch to these issues tomorrow.



Thanks,
Peter

  reply	other threads:[~2009-09-10 21:57 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03  4:14 Staging tree status for the .32 kernel merge Greg KH
2009-09-03  8:49 ` Johannes Berg
2009-09-03 12:48   ` Stefan Lippers-Hollmann
2009-09-03 17:57     ` Greg KH
2009-09-03 18:35       ` Kalle Valo
2009-09-03 19:01         ` Greg KH
2009-09-03 13:14   ` Bartlomiej Zolnierkiewicz
2009-09-03 16:17   ` Christoph Hellwig
2009-09-03 17:55     ` Greg KH
2009-09-03 18:40       ` Christoph Hellwig
2009-09-03 18:55         ` Greg KH
2009-09-03 19:16           ` Christoph Hellwig
2009-09-05  0:16           ` Marcel Holtmann
2009-09-05  0:29             ` Greg KH
2009-09-03 19:35   ` Luis R. Rodriguez
2009-09-03 19:41     ` Greg KH
2009-09-04 10:20 ` Wolfram Sang
2009-09-04 18:25 ` Belisko Marek
2009-09-05 12:39 ` Willy Tarreau
2009-09-05 14:50   ` Greg KH
2009-09-10 21:57     ` Peter Huewe [this message]
2009-09-06  5:28 ` Pavel Machek
2009-09-07 15:55   ` Daniel Walker
2009-09-09  9:57     ` Pavel Machek
2009-09-09 14:19       ` Daniel Walker
2009-09-09  8:01         ` Pavel Machek
2009-09-09 21:47         ` Pavel Machek
2009-09-09 21:53         ` Brian Swetland
2009-09-09 22:25           ` Huntsman, Bryan
2009-09-07 23:12   ` Mauro Carvalho Chehab
2009-09-09  8:10     ` Pavel Machek
2009-09-07 23:21 ` Mauro Carvalho Chehab
2009-09-08  1:14   ` Greg KH
2009-09-12 19:40 ` Frontier USB Drivers (Was: Staging tree status for the .32 kernel merge) Dave Taht
2009-09-14 17:35   ` Greg KH
2009-09-15  9:29     ` Clemens Ladisch

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=200909102357.27867.PeterHuewe@gmx.de \
    --to=peterhuewe@gmx.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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