All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: John Kim <john@larvalstage.com>
Cc: linux-kernel@vger.kernel.org, marcelo@conectiva.com.br,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [PATCH] 2.4.20 compile fix for drivers/scsi/t128.c
Date: Tue, 10 Dec 2002 00:49:58 +0100	[thread overview]
Message-ID: <3DF52C26.2020708@domdv.de> (raw)
In-Reply-To: <Pine.LNX.4.50L0.0212091638400.24225-100000@quinn.larvalstage.com>

I did already submit this, it's in the AC tree and via Alan in Marcelo's 
BK tree:

http://linux.bkbits.net:8080/linux-2.4/diffs/drivers/scsi/t128.c@1.4?nav=index.html|ChangeSet@-7d|cset@1.757.28.37

John Kim wrote:
> Patch below fixes following compile breakage:
> 
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes 
> -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 
> -march=athlon    -nostdinc -iwithprefix
> include -DKBUILD_BASENAME=t128  -c -o t128.o t128.c
> t128.c:148: signatures causes a section type conflict
> NCR5380.c:458: warning: `NCR5380_print_phase' defined but not used
> NCR5380.c:402: warning: `NCR5380_print' defined but not used
> make[3]: *** [t128.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.20/drivers/scsi'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.20/drivers/scsi'
> make[1]: *** [_subdir_scsi] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.20/drivers'
> make: *** [_dir_drivers] Error 2
> 
> 
> 
> diff -Naur linux-2.4.20/drivers/scsi/t128.c linux-2.4.20-new/drivers/scsi/t128.c
> --- linux-2.4.20/drivers/scsi/t128.c	2001-12-21 12:41:55.000000000 -0500
> +++ linux-2.4.20-new/drivers/scsi/t128.c	2002-12-09 12:52:21.000000000 -0500
> @@ -142,7 +142,7 @@
>  
>  #define NO_BASES (sizeof (bases) / sizeof (struct base))
>  
> -static const struct signature {
> +static struct signature {
>  	const char *string;
>  	int offset;
>  } signatures[] __initdata = {
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH


      reply	other threads:[~2002-12-09 23:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 21:44 [PATCH] 2.4.20 compile fix for drivers/scsi/t128.c John Kim
2002-12-09 23:49 ` Andreas Steinmetz [this message]

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=3DF52C26.2020708@domdv.de \
    --to=ast@domdv.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=john@larvalstage.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.