From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mich Lanners <mlan@cpu.lu>
Cc: linuxppc-dev@ozlabs.org, v4l-dvb-maintainer@linuxtv.org,
mchehab@infradead.org, linux-kernel@vger.kernel.org,
Adrian Bunk <bunk@stusta.de>
Subject: Re: [RFC: 2.6 patch] remove the broken VIDEO_PLANB driver
Date: Fri, 05 Jan 2007 09:35:26 +1100 [thread overview]
Message-ID: <1167950126.5273.31.camel@localhost.localdomain> (raw)
In-Reply-To: <tkrat.5fdfdb1db356c580@cpu.lu>
> If you need explanations about the code or the hardware, don't hesitate
> to ask. Not sure what I still remember, but I still have my old paper
> notes.
Heh, ok. No idea when I'll have time to look tho.
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mich Lanners <mlan@cpu.lu>
Cc: Adrian Bunk <bunk@stusta.de>,
linuxppc-dev@ozlabs.org, v4l-dvb-maintainer@linuxtv.org,
linux-kernel@vger.kernel.org, mchehab@infradead.org
Subject: Re: [RFC: 2.6 patch] remove the broken VIDEO_PLANB driver
Date: Fri, 05 Jan 2007 09:35:26 +1100 [thread overview]
Message-ID: <1167950126.5273.31.camel@localhost.localdomain> (raw)
In-Reply-To: <tkrat.5fdfdb1db356c580@cpu.lu>
> If you need explanations about the code or the hardware, don't hesitate
> to ask. Not sure what I still remember, but I still have my old paper
> notes.
Heh, ok. No idea when I'll have time to look tho.
Ben.
next prev parent reply other threads:[~2007-01-04 22:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 18:53 [RFC: 2.6 patch] remove the broken VIDEO_PLANB driver Adrian Bunk
2007-01-04 18:53 ` Adrian Bunk
2007-01-04 21:34 ` Benjamin Herrenschmidt
2007-01-04 21:34 ` Benjamin Herrenschmidt
2007-01-04 22:00 ` Mich Lanners
2007-01-04 22:35 ` Benjamin Herrenschmidt [this message]
2007-01-04 22:35 ` Benjamin Herrenschmidt
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=1167950126.5273.31.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mchehab@infradead.org \
--cc=mlan@cpu.lu \
--cc=v4l-dvb-maintainer@linuxtv.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.