From: Andrew Morton <akpm@osdl.org>
To: Dave Airlie <airlied@gmail.com>
Cc: dmunsie@cecropia.com, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: intelfb vsync and i2c support
Date: Mon, 3 Jul 2006 03:01:39 -0700 [thread overview]
Message-ID: <20060703030139.cd4c7807.akpm@osdl.org> (raw)
In-Reply-To: <21d7e9970607030257u7d73778cv8c6061a1cf59b756@mail.gmail.com>
On Mon, 3 Jul 2006 19:57:53 +1000
"Dave Airlie" <airlied@gmail.com> wrote:
> Andrew can you drop the i915fb branch (which I think you did already)
> and add the intelfb-mm branch to -mm?
OK,
git+ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/intelfb-2.6#intelfb-mm
it is.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
prev parent reply other threads:[~2006-07-03 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 9:57 intelfb vsync and i2c support Dave Airlie
2006-07-03 10:01 ` Andrew Morton [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=20060703030139.cd4c7807.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=airlied@gmail.com \
--cc=dmunsie@cecropia.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).