linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
	paulus@samba.org, netdev@vger.kernel.org
Subject: Re: [PATCH] [POWERPC] iSeries: fix section mismatch in iseries_veth
Date: Tue, 05 Feb 2008 13:32:33 -0500	[thread overview]
Message-ID: <47A8ABC1.9080008@pobox.com> (raw)
In-Reply-To: <20080205141940.c6ddb479.sfr@canb.auug.org.au>

Stephen Rothwell wrote:
> WARNING: vmlinux.o(.text+0x25dca0): Section mismatch in reference from the function .veth_probe() to the function .init.text:.veth_probe_one()
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  drivers/net/iseries_veth.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> Jeff, can this go in through the powerpc tree?
> 
> diff --git a/drivers/net/iseries_veth.c b/drivers/net/iseries_veth.c
> index 419861c..58d3bb6 100644
> --- a/drivers/net/iseries_veth.c
> +++ b/drivers/net/iseries_veth.c
> @@ -1020,7 +1020,7 @@ static const struct ethtool_ops ops = {
>  	.get_link = veth_get_link,
>  };
>  
> -static struct net_device * __init veth_probe_one(int vlan,
> +static struct net_device *veth_probe_one(int vlan,
>  		struct vio_dev *vio_dev)
>  {


it's trivial enough to not matter, and faster to just...  applied
(if you'll pardon the bad grammar)

  reply	other threads:[~2008-02-05 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  3:19 [PATCH] [POWERPC] iSeries: fix section mismatch in iseries_veth Stephen Rothwell
2008-02-05 18:32 ` Jeff Garzik [this message]
2008-02-06 12:11   ` Stephen Rothwell

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=47A8ABC1.9080008@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).