From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] hpt366: fix section mismatch warnings
Date: Fri, 22 Feb 2008 22:53:42 +0300 [thread overview]
Message-ID: <47BF2846.1030604@ru.mvista.com> (raw)
In-Reply-To: <20080222194651.GA7154@uranus.ravnborg.org>
Sam Ravnborg wrote:
> hpt366: fix section mismatch warnings
> Fix following warnings:
> WARNING: o-sparc64/vmlinux.o(.data+0x195a38): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370
> WARNING: o-sparc64/vmlinux.o(.data+0x195a40): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt370a
> WARNING: o-sparc64/vmlinux.o(.data+0x195a48): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt372
> WARNING: o-sparc64/vmlinux.o(.data+0x195a50): Section mismatch in reference from the variable hpt37x_info.0 to the variable .devinit.data:hpt372n
> Replace a static array with a small switch resulting in
> more readable code.
> Be consistent in use of __devinitconst for const data
> to avoid section type conflicts.
> Mark the pci table __devinitconst.
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
Acked-by: Sergei Shtylyov <sshtylyov@ru.mvista.com>
MBR, Sergei
next prev parent reply other threads:[~2008-02-22 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 19:46 [PATCH] hpt366: fix section mismatch warnings Sam Ravnborg
2008-02-22 19:53 ` Sergei Shtylyov [this message]
2008-02-22 20:57 ` Bartlomiej Zolnierkiewicz
2008-02-22 20:43 ` Sam Ravnborg
2008-02-23 21:22 ` [Fixed PATCH] " Sam Ravnborg
2008-02-24 14:33 ` Bartlomiej Zolnierkiewicz
2008-02-24 17:53 ` Sam Ravnborg
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=47BF2846.1030604@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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