netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Adrian Bunk <bunk@kernel.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for September 13 (3c509)
Date: Mon, 15 Sep 2008 16:27:24 +0200	[thread overview]
Message-ID: <48CE70CC.7020901@suse.de> (raw)
In-Reply-To: <20080915141149.GA10002@cs181140183.pp.htv.fi>

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

Hi Adrian,

Adrian Bunk wrote:
> On Sun, Sep 14, 2008 at 02:17:57PM -0700, Randy Dunlap wrote:
>> drivers/net/3c509.c fails (CONFIG_PM=y) with:
>>
>> drivers/built-in.o:(.data+0x7dcc): undefined reference to `el3_resume'
>> drivers/built-in.o:(.data+0x7e08): undefined reference to `el3_resume'
>>
>> It seems that this function does not exist in the source file.
> 
> 
> It got removed by:
> 
> 
> commit 107aeb9753159da848f066b26557f0aaab900a90
> Author: Hannes Reinecke <hare@suse.de>
> Date:   Wed Sep 10 14:16:04 2008 +0200
> 
>     Driver core: Use dev_get_drvdata() accessors
>     
>     Deprecated direct access to the ->driver_data field and
>     use accessors throughout.
>     
>     Signed-off-by: Hannes Reinecke <hare@suse.de>
>     Cc: Kay Sievers <kay.sievers@vrfy.org>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> 
Sorry. Here it is again.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

[-- Attachment #2: 3c509-readd-el3_resume --]
[-- Type: text/plain, Size: 621 bytes --]

Re-add el3_resume to 3c509

In commit 107aeb9753159da848f066b26557f0aaab900a90
el3_resume() from drivers/net/3c509.c accidentally got
removed. Re-add it.

Signed-off-by: Hannes Reinecke <hare@suse.de>

diff --git a/drivers/net/3c509.c b/drivers/net/3c509.c
index b33f7d9..6ace220 100644
--- a/drivers/net/3c509.c
+++ b/drivers/net/3c509.c
@@ -1493,6 +1493,15 @@ el3_common_resume(struct net_device *dev)
 	return 0;
 }
 
+static int
+el3_resume(struct device *pdev)
+{
+	struct net_device *dev;
+
+	dev = dev_get_drvdata(pdev);
+	return el3_common_resume(dev);
+}
+
 #endif /* CONFIG_PM */
 
 module_param(debug,int, 0);

  reply	other threads:[~2008-09-15 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080913162344.ab395285.sfr@canb.auug.org.au>
2008-09-14 21:17 ` linux-next: Tree for September 13 (3c509) Randy Dunlap
2008-09-15 14:11   ` Adrian Bunk
2008-09-15 14:27     ` Hannes Reinecke [this message]
2008-09-15 15:03       ` Randy Dunlap
2008-09-15 18:55         ` Greg KH

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=48CE70CC.7020901@suse.de \
    --to=hare@suse.de \
    --cc=bunk@kernel.org \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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).