All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: marcelo.tosatti@cyclades.com
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [TRIVIAL PATCH] 2.4.25pre7 warning fix
Date: Tue, 27 Jan 2004 22:28:12 +0100	[thread overview]
Message-ID: <m3u12hcc9f.fsf@defiant.pm.waw.pl> (raw)

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

Hi,

The attached patch fixes the following warning msg:

time.c:435: warning: `do_gettimeoffset_cyclone' defined but not used

There is no need to define functions which do just { return 0; } and
which aren't called by anything.

(In case CONFIG_X86_SUMMIT is defined, there is another (real)
do_gettimeoffset_cyclone() function, and it is referenced - but
it's simply not related to this empty function).

Please apply to 2.4 kernel tree. Thanks.
-- 
Krzysztof Halasa, B*FH

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: time-2.4.23pre9.patch --]
[-- Type: text/x-patch, Size: 433 bytes --]

--- linux-2.4.orig/arch/i386/kernel/time.c	2003-10-24 22:48:15.000000000 +0200
+++ linux-2.4/arch/i386/kernel/time.c	2003-11-09 17:38:18.000000000 +0100
@@ -430,7 +430,6 @@
 
 const int use_cyclone = 0;
 static void mark_timeoffset_cyclone(void) {}
-static unsigned long do_gettimeoffset_cyclone(void) {return 0;}
 static void init_cyclone_clock(void) {}
 void __cyclone_delay(unsigned long loops) {}
 #endif /* CONFIG_X86_SUMMIT */

             reply	other threads:[~2004-01-27 22:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 21:28 Krzysztof Halasa [this message]
2004-01-28 11:42 ` [TRIVIAL PATCH] 2.4.25pre7 warning fix Marcelo Tosatti
2004-01-28 22:17   ` Krzysztof Halasa
2004-01-29 16:38   ` Krzysztof Halasa
2004-01-29 19:22     ` john stultz

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=m3u12hcc9f.fsf@defiant.pm.waw.pl \
    --to=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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.