From: Randy Dunlap <randy.dunlap@oracle•com>
To: lkml <linux-kernel@vger•kernel.org>
Cc: linux-next@vger•kernel.org, Bob Beers <bob.beers@gmail•com>,
gregkh@suse•de
Subject: [PATCH -next] staging/cxt1e1: use netdev_priv to fix build
Date: Fri, 30 Apr 2010 10:07:12 -0700 [thread overview]
Message-ID: <20100430100712.041f6fcc.randy.dunlap@oracle.com> (raw)
From: Randy Dunlap <randy.dunlap@oracle•com>
Fix cxt1e1 build error:
drivers/staging/cxt1e1/linux.c:1195: error: 'struct net_device' has no member named 'priv'
Signed-off-by: Randy Dunlap <randy.dunlap@oracle•com>
Cc: Bob Beers <bob.beers@gmail•com>
---
drivers/staging/cxt1e1/linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20100430.orig/drivers/staging/cxt1e1/linux.c
+++ linux-next-20100430/drivers/staging/cxt1e1/linux.c
@@ -1192,7 +1192,7 @@ c4_add_dev (hdw_info_t * hi, int brdno,
hi->devname, irq1);
unregister_netdev (ndev);
free_irq (irq0, ndev);
- OS_kfree (ndev->priv);
+ OS_kfree (netdev_priv(ndev));
OS_kfree (ndev);
error_flag = EIO;
return 0;
next reply other threads:[~2010-04-30 17:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-30 17:07 Randy Dunlap [this message]
2010-04-30 18:19 ` [PATCH -next] staging/cxt1e1: use netdev_priv to fix build Bob Beers
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=20100430100712.041f6fcc.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=bob.beers@gmail$(echo .)com \
--cc=gregkh@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/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