From: Greg KH <gregkh@linuxfoundation•org>
To: David Miller <davem@davemloft•net>
Cc: fengguang.wu@intel•com, wfp5p@virginia•edu, netdev@vger•kernel.org
Subject: Re: WARNING: drivers/net/ethernet/broadcom/tg3.o(.text+0x16006): Section mismatch in reference from the function tg3_get_invariants() to the variable .devinit.rodata:tg3_write_reorder_chipsets
Date: Tue, 4 Dec 2012 12:30:25 -0800 [thread overview]
Message-ID: <20121204203025.GA32674@kroah.com> (raw)
In-Reply-To: <20121204.152825.1014358628158241121.davem@davemloft.net>
On Tue, Dec 04, 2012 at 03:28:25PM -0500, David Miller wrote:
> From: kbuild test robot <fengguang.wu@intel•com>
> Date: Wed, 05 Dec 2012 04:24:21 +0800
>
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> > head: 193c1e478cc496844fcbef402a10976c95a634ff
> > commit: 229b1ad1cb1a7159658f466c736bc3898dabb876 tg3: remove __dev* attributes
> > date: 25 hours ago
> > config: make ARCH=x86_64 allmodconfig
> >
> > All warnings:
>
> This is a result of the __dev* macro removal from the networking
> drivers. I think it will be resolved when Greg KH's tree gets merged.
>
> The issue is that the PCI device ID macros in linux/pci.h still
> use the __dev* tags.
>
> Greg, please confirm.
Yes, that is correct. Fengguang, you can stop reporting these kinds of
warnings, you are going to get a bunch of them from now until 3.8-rc1 is
out.
thanks,
greg k-h
prev parent reply other threads:[~2012-12-04 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 20:24 WARNING: drivers/net/ethernet/broadcom/tg3.o(.text+0x16006): Section mismatch in reference from the function tg3_get_invariants() to the variable .devinit.rodata:tg3_write_reorder_chipsets kbuild test robot
2012-12-04 20:28 ` David Miller
2012-12-04 20:30 ` Greg KH [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=20121204203025.GA32674@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=fengguang.wu@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=wfp5p@virginia$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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