From: Hannes Eder <hannes@hanneseder.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: David Airlie <airlied@linux.ie>
Subject: [PATCH v2 6/6] drm/i915: un-EXPORT and make 'intelfb_panic' static
Date: Fri, 19 Dec 2008 11:34:27 +0000 [thread overview]
Message-ID: <494b8afb.0aa5660a.589f.fffffd82@mx.google.com> (raw)
In-Reply-To: <200812181540.08366.jbarnes@virtuousgeek.org>
Fix this sparse warning:
drivers/gpu/drm/i915/intel_fb.c:417:5: warning: symbol 'intelfb_panic' was not declared. Should it be static?
Signed-off-by: Hannes Eder <hannes@hanneseder.net>
---
On Fri, Dec 19, 2008 at 12:40 AM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Thursday, December 18, 2008 1:32 pm Hannes Eder wrote:
>> Fix this sparse warning:
>>
>> drivers/gpu/drm/i915/intel_fb.c:417:5: warning: symbol 'intelfb_panic'
>> was not declared. Should it be static?
>
> Yep, this one should be static instead (I think, just double checking now to
> make sure it's not used elsewhere, iirc it's not).
Ok, so let's make the function static and there is no need to EXPORT
it, which wouldn't work for a static function anyway.
When is it safe to un-EXPORT a function? When it is only referenced
within the translation unit it is defined in? But it could be
referenced from outside the kernel source, or?
drivers/gpu/drm/i915/intel_fb.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_fb.c b/drivers/gpu/drm/i915/intel_fb.c
index 12664c3..bbf6fe0 100644
--- a/drivers/gpu/drm/i915/intel_fb.c
+++ b/drivers/gpu/drm/i915/intel_fb.c
@@ -414,15 +414,14 @@ EXPORT_SYMBOL(intelfb_resize);
static struct drm_mode_set kernelfb_mode;
-int intelfb_panic(struct notifier_block *n, unsigned long ununsed,
- void *panic_str)
+static int intelfb_panic(struct notifier_block *n, unsigned long ununsed,
+ void *panic_str)
{
DRM_ERROR("panic occurred, switching back to text console\n");
intelfb_restore();
return 0;
}
-EXPORT_SYMBOL(intelfb_panic);
static struct notifier_block paniced = {
.notifier_call = intelfb_panic,
--
1.5.6.3
WARNING: multiple messages have this Message-ID (diff)
From: Hannes Eder <hannes@hanneseder.net>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org
Subject: [PATCH v2 6/6] drm/i915: un-EXPORT and make 'intelfb_panic' static
Date: Fri, 19 Dec 2008 12:34:27 +0100 [thread overview]
Message-ID: <494b8afb.0aa5660a.589f.fffffd82@mx.google.com> (raw)
In-Reply-To: <200812181540.08366.jbarnes@virtuousgeek.org>
Fix this sparse warning:
drivers/gpu/drm/i915/intel_fb.c:417:5: warning: symbol 'intelfb_panic' was not declared. Should it be static?
Signed-off-by: Hannes Eder <hannes@hanneseder.net>
---
On Fri, Dec 19, 2008 at 12:40 AM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Thursday, December 18, 2008 1:32 pm Hannes Eder wrote:
>> Fix this sparse warning:
>>
>> drivers/gpu/drm/i915/intel_fb.c:417:5: warning: symbol 'intelfb_panic'
>> was not declared. Should it be static?
>
> Yep, this one should be static instead (I think, just double checking now to
> make sure it's not used elsewhere, iirc it's not).
Ok, so let's make the function static and there is no need to EXPORT
it, which wouldn't work for a static function anyway.
When is it safe to un-EXPORT a function? When it is only referenced
within the translation unit it is defined in? But it could be
referenced from outside the kernel source, or?
drivers/gpu/drm/i915/intel_fb.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_fb.c b/drivers/gpu/drm/i915/intel_fb.c
index 12664c3..bbf6fe0 100644
--- a/drivers/gpu/drm/i915/intel_fb.c
+++ b/drivers/gpu/drm/i915/intel_fb.c
@@ -414,15 +414,14 @@ EXPORT_SYMBOL(intelfb_resize);
static struct drm_mode_set kernelfb_mode;
-int intelfb_panic(struct notifier_block *n, unsigned long ununsed,
- void *panic_str)
+static int intelfb_panic(struct notifier_block *n, unsigned long ununsed,
+ void *panic_str)
{
DRM_ERROR("panic occurred, switching back to text console\n");
intelfb_restore();
return 0;
}
-EXPORT_SYMBOL(intelfb_panic);
static struct notifier_block paniced = {
.notifier_call = intelfb_panic,
--
1.5.6.3
next prev parent reply other threads:[~2008-12-19 11:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 21:32 [PATCH 6/6] drm/i915: add prototype for 'intelfb_panic' to header file Hannes Eder
2008-12-18 21:32 ` Hannes Eder
2008-12-18 23:40 ` Jesse Barnes
2008-12-18 23:40 ` Jesse Barnes
2008-12-19 11:34 ` Hannes Eder [this message]
2008-12-19 11:34 ` [PATCH v2 6/6] drm/i915: un-EXPORT and make 'intelfb_panic' static Hannes Eder
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=494b8afb.0aa5660a.589f.fffffd82@mx.google.com \
--to=hannes@hanneseder.net \
--cc=airlied@linux.ie \
--cc=jbarnes@virtuousgeek.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.