From: Dave Airlie <airlied@linux.ie>
To: torvalds@osdl.org, Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] intelfb cleanup
Date: Sat, 24 Jun 2006 08:49:11 +0100 (IST) [thread overview]
Message-ID: <Pine.LNX.4.64.0606240848210.30220@skynet.skynet.ie> (raw)
Hi Linus,
Can you pull the intelfb-patches branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/airlied/intelfb-2.6
It contains a cleanup from Al for some really brutal previous efforts
at sparse cleanups.
Dave.
drivers/video/intelfb/intelfb.h | 2 +-
drivers/video/intelfb/intelfbdrv.c | 18 +++++++++---------
drivers/video/intelfb/intelfbhw.c | 24 ++++++++++--------------
3 files changed, 20 insertions(+), 24 deletions(-)
commit 0fe6e2d2928e089d16ec5ed7ba634c1d60916020
Author: Al Viro <viro@ftp.linux.org.uk>
Date: Fri Jun 23 06:05:39 2006 +0100
intelfb delousing
ring_head is offset in card memory, not iomem pointer. Fixed, removed
fuckloads of amazingly bogus casts somebody had sprinkled all over the
place.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Dave Airlie <airlied@linux.ie>
reply other threads:[~2006-06-24 7:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.0606240848210.30220@skynet.skynet.ie \
--to=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).