public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bryan Batten <BryanBatten@compuserve.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Rich Liu <richliu@poorman.org>,
	Trivial Patch Monkey <trivial@rustcorp.com.au>,
	linux-kernel@vger.kernel.org
Subject: [PATCH]-2.6.10-rc2: Fix Compiler Warning parport_pc.c
Date: Thu, 18 Nov 2004 11:09:48 -0800	[thread overview]
Message-ID: <419CF37C.7050000@compuserve.com> (raw)

After patching up to 2.6.10-rc2, I get the following compiler warning
when building the kernel with gcc 2.95:

drivers/parport/parport_pc.c:3317: warning: initialization from incompatible pointer type

The warning occurs because parport_init_mode_setup() wants 'char *'
instead of 'const char *'.

The fix is to just remove the 'const' from the declaration.

Here's the patch to drivers/parport/parport_pc.c:
--------------------------------snip-snip-----------------------------
# diff -up *orig/drivers/parport/parport_pc.c *6x/drivers/parport
--- linux-2.6.9orig/drivers/parport/parport_pc.c        Mon Nov 15 22:44:11 2004
+++ linux-2.6x/drivers/parport/parport_pc.c     Wed Nov 17 22:35:37 2004
@@ -3154,7 +3154,7 @@ static int __init parport_parse_dma(cons
                                      PARPORT_DMA_NONE, PARPORT_DMA_NOFIFO);
  }

-static int __init parport_init_mode_setup(const char *str) {
+static int __init parport_init_mode_setup(char *str) {

         printk(KERN_DEBUG "parport_pc.c: Specified parameter parport_init_mode=%s\n", str);

------------------------------end-snip-snip---------------------------

(Signed-off-by: Bryan Batten <BryanBatten@compuserve.com>)







                 reply	other threads:[~2004-11-18 19:13 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=419CF37C.7050000@compuserve.com \
    --to=bryanbatten@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richliu@poorman.org \
    --cc=trivial@rustcorp.com.au \
    /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