From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Krzysztof Helt <krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w@public.gmane.org>
Cc: Linux-fbdev-devel
<linux-fbdev-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Subject: Re: [PATCH 1/2] tdfxfb: move I2C functionality into the tdfxfb
Date: Tue, 24 Mar 2009 08:58:39 +0100 [thread overview]
Message-ID: <20090324085839.43a6b496@hyperion.delvare> (raw)
In-Reply-To: <20090323192637.b820f669.krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w@public.gmane.org>
On Mon, 23 Mar 2009 19:26:37 +0100, Krzysztof Helt wrote:
> From: Krzysztof Helt <krzysztof.h1-5tc4TXWwyLM@public.gmane.org>
>
> The I2C functionality provided by the i2c-voodoo3 driver
> is moved into the tdfxfb (frame buffer driver for Voodoo3
> cards). This way there is no conflict between the i2c driver
> and the fb driver.
>
> The tdfxfb does not make use from the DDC functionality yet
> but provides all the functionality of the i2c-voodoo3 driver.
>
> Signed-off-by: Krzysztof Helt <krzysztof.h1-5tc4TXWwyLM@public.gmane.org>
Acked-by: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
> ---
> I prefer to send these patches through Andrew Morton's
> tree as the second patch is not related to the i2c stuff.
>
> Both patches are for the -mm tree.
Fine with me.
>
> drivers/video/Kconfig | 9 ++
> drivers/video/tdfxfb.c | 200 +++++++++++++++++++++++++++++++++++++++++++++++-
> include/video/tdfx.h | 26 ++++++
> 3 files changed, 234 insertions(+), 1 deletions(-)
>
> (...)
--
Jean Delvare
prev parent reply other threads:[~2009-03-24 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 18:26 [PATCH 1/2] tdfxfb: move I2C functionality into the tdfxfb Krzysztof Helt
[not found] ` <20090323192637.b820f669.krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w@public.gmane.org>
2009-03-24 7:58 ` Jean Delvare [this message]
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=20090324085839.43a6b496@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=krzysztof.h1-IjDXvh/HVVUAvxtiuMwx3w@public.gmane.org \
--cc=linux-fbdev-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox