From: Greg KH <gregkh@linuxfoundation.org>
To: Ian Abbott <abbotti@mev.co.uk>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Ian Abbott <ian.abbott@mev.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"fmhess@users.sourceforge.net" <fmhess@users.sourceforge.net>
Subject: Re: [PATCH v2] staging: comedi: resolve section mismatch in s626
Date: Fri, 20 Apr 2012 08:33:31 -0700 [thread overview]
Message-ID: <20120420153331.GA19219@kroah.com> (raw)
In-Reply-To: <20120420013411.GA3769@cantor.Home>
On Thu, Apr 19, 2012 at 06:34:11PM -0700, Gerard Snitselaar wrote:
> I am getting an error when doing a build of the latest linux-next
> before it gets to modpost so I need to look at that, but when I do an
> allyesconfig build on master I get the following:
>
> WARNING: drivers/staging/comedi/drivers/s626.o(.text+0x2ec8): Section mismatch in reference from the function s626_attach() to the variable .devinit.rodata:s626_pci_table
> The function s626_attach() references
> the variable __devinitconst s626_pci_table.
> This is often because s626_attach lacks a __devinitconst
> annotation or the annotation of s626_pci_table is wrong.
>
> WARNING: drivers/staging/comedi/drivers/s626.o(.text+0x2ece): Section mismatch in reference from the function s626_attach() to the variable .devinit.rodata:s626_pci_table
> The function s626_attach() references
> the variable __devinitconst s626_pci_table.
> This is often because s626_attach lacks a __devinitconst
> annotation or the annotation of s626_pci_table is wrong.
>
> WARNING: drivers/staging/comedi/drivers/s626.o(.text+0x2ed7): Section mismatch in reference from the function s626_attach() to the variable .devinit.rodata:s626_pci_table
> The function s626_attach() references
> the variable __devinitconst s626_pci_table.
> This is often because s626_attach lacks a __devinitconst
> annotation or the annotation of s626_pci_table is wrong.
>
> WARNING: drivers/staging/comedi/drivers/s626.o(.text+0x2edd): Section mismatch in reference from the function s626_attach() to the variable .devinit.rodata:s626_pci_table
> The function s626_attach() references
> the variable __devinitconst s626_pci_table.
> This is often because s626_attach lacks a __devinitconst
> annotation or the annotation of s626_pci_table is wrong.
Odd, can you send me your .config file?
Also, I don't have this patch in my queue anymore, can someone please
resend it if it is to be applied?
greg k-h
next prev parent reply other threads:[~2012-04-20 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 2:25 [PATCH] staging: comedi: resolve section mismatch in s626 Gerard Snitselaar
2012-03-19 3:09 ` [PATCH v2] " Gerard Snitselaar
2012-03-19 16:31 ` Greg KH
2012-03-19 16:43 ` Gerard Snitselaar
2012-03-19 22:46 ` Gerard Snitselaar
2012-03-19 23:26 ` Greg KH
2012-04-02 10:48 ` Ian Abbott
2012-04-10 18:24 ` Greg KH
2012-04-10 19:24 ` Gerard Snitselaar
2012-04-12 13:03 ` Ian Abbott
2012-04-18 23:28 ` Greg KH
2012-04-20 1:34 ` Gerard Snitselaar
2012-04-20 15:33 ` Greg KH [this message]
2012-04-24 1:30 ` [PATCH v2 resend] " Gerard Snitselaar
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=20120420153331.GA19219@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=ian.abbott@mev.co.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