All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pauline Middelink <middelink@polyware.nl>
To: Michael Krufky <mkrufky@m1k.net>
Cc: gcoady@gmail.com, Mauro Carvalho Chehab <mchehab@brturbo.com.br>,
	Linus Torvalds <torvalds@osdl.org>,
	Eyal Lebedinsky <eyal@eyal.emu.id.au>,
	list linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.15-rc4
Date: Fri, 2 Dec 2005 20:37:26 +0100	[thread overview]
Message-ID: <20051202193725.GA32346@polyware.nl> (raw)
In-Reply-To: <43908900.5070504@m1k.net>

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

On Fri, 02 Dec 2005 around 12:48:48 -0500, Michael Krufky wrote:

> >I gave up on it, offered to kill it for 2.6.14-rc2-mm1, you want a 
> >freshened removal patch?
> > 
> >
> No, Mauro, Pauline already told us that she's working on it.....
> 
> Poor Pauline, about once a month someone wants to nuke ZR36120.

Grumble, its a conspiracy :)

> Instead of nuking it, let's just mark it BROKEN for now...

That would be preferable.

> Pauline, what's the status?

For one, the machine I was testing with made proper use of large memory
pointers to stribble all over its memory and erase essencial parts of
its disk structures. :(

Half way I would say. During the upcoming free days I hope to find the
time to finish it up so the driver works with current i2c, v4l and
memory.


    Met vriendelijke groet,
        Pauline Middelink
-- 
GPG Key fingerprint = 2D5B 87A7 DDA6 0378 5DEA  BD3B 9A50 B416 E2D0 C3C2
For more details look at my website http://www.polyware.nl/~middelink

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2276 bytes --]

  reply	other threads:[~2005-12-02 19:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01  6:40 Linux 2.6.15-rc4 Linus Torvalds
2005-12-01 12:18 ` Ralf Hildebrandt
2005-12-01 21:11   ` Terence Ripperda
2005-12-01 23:11     ` Linus Torvalds
2005-12-02 18:02       ` Terence Ripperda
2005-12-03  0:22         ` Greg KH
     [not found]           ` <6f6293f10512031726n10ea87e6s44be5dffbd512bb5@mail.gmail.com>
2005-12-04  1:34             ` Linus Torvalds
2005-12-01 14:05 ` Kasper Sandberg
2005-12-01 16:05   ` Linus Torvalds
2005-12-01 18:57     ` Kasper Sandberg
2005-12-01 19:04       ` Linus Torvalds
2005-12-01 22:57         ` Kasper Sandberg
     [not found]     ` <6f6293f10512011112m6e50fe0ejf0aa5ba9d09dca1e@mail.gmail.com>
2005-12-01 19:34       ` Linus Torvalds
2005-12-01 21:41         ` Eyal Lebedinsky
2005-12-01 21:53           ` Linus Torvalds
2005-12-01 23:37             ` Grant Coady
2005-12-02 11:45               ` Mauro Carvalho Chehab
2005-12-02 17:41                 ` Grant Coady
2005-12-02 17:48                   ` Michael Krufky
2005-12-02 19:37                     ` Pauline Middelink [this message]
2005-12-02 20:19                       ` Grant Coady
2005-12-02 20:32                         ` Richard Mittendorfer
2005-12-04 15:50                     ` Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2005-12-04  3:00 Paul Blazejowski
2005-12-04 14:12 Subodh Shrivastava
2005-12-05 15:51 ` Mark Lord

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=20051202193725.GA32346@polyware.nl \
    --to=middelink@polyware.nl \
    --cc=eyal@eyal.emu.id.au \
    --cc=gcoady@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@brturbo.com.br \
    --cc=mkrufky@m1k.net \
    --cc=torvalds@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.