From: Domen Puncer <domen@coderock.org>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] [patch 2.6.6] remove faulty __init's from
Date: Mon, 17 May 2004 19:08:33 +0000 [thread overview]
Message-ID: <20040517190833.GC5034@nd47> (raw)
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
Hi.
These four are called from fb_show_logo, which is exported symbol,
called by fbcon_switch.
Compile tested.
Domen
--- c/drivers/video/fbmem.c 2004-05-10 14:16:10.000000000 +0200
+++ a/drivers/video/fbmem.c 2004-05-17 19:48:37.000000000 +0200
@@ -509,7 +509,7 @@ static inline unsigned safe_shift(unsign
return n < 0 ? d >> -n : d << n;
}
-static void __init fb_set_logocmap(struct fb_info *info,
+static void fb_set_logocmap(struct fb_info *info,
const struct linux_logo *logo)
{
struct fb_cmap palette_cmap;
@@ -543,7 +543,7 @@ static void __init fb_set_logocmap(struc
}
}
-static void __init fb_set_logo_truepalette(struct fb_info *info,
+static void fb_set_logo_truepalette(struct fb_info *info,
const struct linux_logo *logo,
u32 *palette)
{
@@ -573,7 +573,7 @@ static void __init fb_set_logo_truepale
}
}
-static void __init fb_set_logo_directpalette(struct fb_info *info,
+static void fb_set_logo_directpalette(struct fb_info *info,
const struct linux_logo *logo,
u32 *palette)
{
@@ -588,7 +588,7 @@ static void __init fb_set_logo_directpal
palette[i] = i << redshift | i << greenshift | i << blueshift;
}
-static void __init fb_set_logo(struct fb_info *info,
+static void fb_set_logo(struct fb_info *info,
const struct linux_logo *logo, u8 *dst,
int depth)
{
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
reply other threads:[~2004-05-17 19:08 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=20040517190833.GC5034@nd47 \
--to=domen@coderock.org \
--cc=kernel-janitors@vger.kernel.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.