From: Andreas Steinmetz <ast@domdv.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4.20rc1 compile fix for t128.c
Date: Mon, 04 Nov 2002 15:16:40 +0100 [thread overview]
Message-ID: <3DC68148.3070307@domdv.de> (raw)
In-Reply-To: 1036419832.1106.50.camel@irongate.swansea.linux.org.uk
[forgot to cc lkml]
Alan Cox wrote:
> On Mon, 2002-11-04 at 13:37, Andreas Steinmetz wrote:
>
>>The attached patch fixes a section type conflict error.
>
>
> Which compiler is showing this problem ?
>
gcc 3.2
>
>>--- ./drivers/scsi/t128.c.orig 2002-11-04 14:21:30.000000000 +0100
>>+++ ./drivers/scsi/t128.c 2002-11-04 14:21:47.000000000 +0100
>>@@ -145,7 +145,7 @@
>> static const struct signature {
>> const char *string;
>> int offset;
>>-} signatures[] __initdata = {
>>+} signatures[] = {
>> {"TSROM: SCSI BIOS, Version 1.12", 0x36},
>
>
> Far better to lose the const
>
any way you please.
>
--
Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
prev parent reply other threads:[~2002-11-04 14:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 13:37 [PATCH] 2.4.20rc1 compile fix for t128.c Andreas Steinmetz
2002-11-04 14:23 ` Alan Cox
2002-11-04 14:16 ` 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=3DC68148.3070307@domdv.de \
--to=ast@domdv.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox