From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
scsi <linux-scsi@vger.kernel.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 29 (fcoe)
Date: Mon, 29 Dec 2008 14:21:45 -0800 [thread overview]
Message-ID: <49594D79.30806@oracle.com> (raw)
In-Reply-To: <1230587141.3302.64.camel@localhost.localdomain>
James Bottomley wrote:
>
> Actually, I deduce the problem is owner->name and your build has
> CONFIG_MODULE=n ... the definition of struct module is enclosed in a
> #ifdef CONFIG_MODULE.
>
> This should fix it.
>
> James
Ack. Thanks.
> ---
>
> diff --git a/drivers/scsi/fcoe/libfcoe.c b/drivers/scsi/fcoe/libfcoe.c
> index 1cb549c..fec38f6 100644
> --- a/drivers/scsi/fcoe/libfcoe.c
> +++ b/drivers/scsi/fcoe/libfcoe.c
> @@ -992,7 +992,7 @@ static int fcoe_ethdrv_get(const struct net_device *netdev)
> owner = fcoe_netdev_to_module_owner(netdev);
> if (owner) {
> printk(KERN_DEBUG "foce:hold driver module %s for %s\n",
> - owner->name, netdev->name);
> + module_name(owner), netdev->name);
> return try_module_get(owner);
> }
> return -ENODEV;
> @@ -1012,7 +1012,7 @@ static int fcoe_ethdrv_put(const struct net_device *netdev)
> owner = fcoe_netdev_to_module_owner(netdev);
> if (owner) {
> printk(KERN_DEBUG "foce:release driver module %s for %s\n",
> - owner->name, netdev->name);
> + module_name(owner), netdev->name);
> module_put(owner);
> return 0;
> }
>
>
--
~Randy
next prev parent reply other threads:[~2008-12-29 22:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 16:16 linux-next: Tree for December 29 Stephen Rothwell
2008-12-29 20:31 ` linux-next: Tree for December 29 (fcoe) Randy Dunlap
2008-12-29 21:35 ` James Bottomley
2008-12-29 21:45 ` James Bottomley
2008-12-29 22:21 ` Randy Dunlap [this message]
2008-12-29 20:35 ` linux-next: Tree for December 29 (cxgb3i) Randy Dunlap
2008-12-29 21:51 ` James Bottomley
2008-12-29 22:10 ` Randy Dunlap
2008-12-29 21:01 ` [PATCH -next] cxgb3i: use same dependencies as CHELSIO_T3 Randy Dunlap
2008-12-29 21:23 ` [PATCH -next v2] cxgb3i: use same dependencies & selects " Randy Dunlap
2008-12-29 21:58 ` James Bottomley
2008-12-29 22:08 ` Randy Dunlap
2008-12-30 16:20 ` James Bottomley
2008-12-30 3:53 ` linux-next: Tree for December 29 (fcoe/libfc) Randy Dunlap
2008-12-30 15:44 ` James Bottomley
2008-12-30 16:54 ` Randy Dunlap
2008-12-30 17:12 ` James Bottomley
2008-12-30 17:36 ` Randy Dunlap
2008-12-30 17:40 ` Kamalesh Babulal
2008-12-30 15:45 ` [BUILD-FAILURE] fcoe driver build fails with !CONFIG_PCI Kamalesh Babulal
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=49594D79.30806@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.