From: Randy Dunlap <randy.dunlap@oracle.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
driverdevel <devel@driverdev.osuosl.org>,
gregkh@suse.de
Subject: Re: mmotm 2010-10-13-17-13 uploaded (staging/bcm)
Date: Thu, 14 Oct 2010 13:38:23 -0700 [thread overview]
Message-ID: <4CB76A3F.5070903@oracle.com> (raw)
In-Reply-To: <20101014191447.GF11510@kroah.com>
On 10/14/10 12:14, Greg KH wrote:
> On Wed, Oct 13, 2010 at 09:17:54PM -0700, Randy Dunlap wrote:
>> On Wed, 13 Oct 2010 17:13:25 -0700 akpm@linux-foundation.org wrote:
>>
>>> The mm-of-the-moment snapshot 2010-10-13-17-13 has been uploaded to
>>>
>>> http://userweb.kernel.org/~akpm/mmotm/
>>>
>>> and will soon be available at
>>>
>>> git://zen-kernel.org/kernel/mmotm.git
>>>
>>> It contains the following patches against 2.6.36-rc7:
>>
>>
>> drivers/staging/bcm/Bcmnet.c:24: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:24: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:24: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:26: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:31: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:31: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:31: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:33: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:34: error: 'struct net_device' has no member named 'refcnt'
>> drivers/staging/bcm/Bcmnet.c:35: error: 'struct net_device' has no member named 'refcnt'
>
> Very wierd, is this coming from some other net_device structure change
> in linux-next or mm?
in linux-next:
include/linux/netdevice.h:
< atomic_t refcnt ____cacheline_aligned_in_smp;
> int __percpu *pcpu_refcnt;
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-10-14 20:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 0:13 mmotm 2010-10-13-17-13 uploaded akpm
2010-10-14 4:17 ` mmotm 2010-10-13-17-13 uploaded (staging/bcm) Randy Dunlap
2010-10-14 19:14 ` Greg KH
2010-10-14 20:38 ` Randy Dunlap [this message]
2010-10-14 4:29 ` mmotm 2010-10-13-17-13 uploaded (leds) Randy Dunlap
2010-10-14 11:38 ` Johannes Berg
2010-10-14 16:14 ` Randy Dunlap
2010-10-14 20:13 ` Johannes Berg
2010-10-14 20:32 ` Randy Dunlap
2010-10-26 10:14 ` Johannes Berg
2010-10-14 10:26 ` mmotm 2010-10-13-17-13 uploaded Zimny Lech
2010-10-14 19:16 ` Andrew Morton
2010-10-14 19:23 ` Zimny Lech
2010-10-14 20:06 ` mmotm 2010-10-13 - GSPCA SPCA561 webcam driver broken Valdis.Kletnieks
2010-10-15 8:45 ` Hans Verkuil
2010-10-15 9:05 ` Andrew Morton
2010-10-15 10:02 ` Hans Verkuil
2010-10-15 12:05 ` Mauro Carvalho Chehab
2010-10-15 12:23 ` Hans Verkuil
2010-10-18 19:00 ` Mauro Carvalho Chehab
2010-10-18 19:39 ` Hans Verkuil
2010-10-20 15:50 ` ptrace BUG [was: mmotm 2010-10-13-17-13 uploaded] Jiri Slaby
2010-10-20 15:52 ` Peter Zijlstra
2010-10-20 15:54 ` Frederic Weisbecker
2010-10-20 16:03 ` Jiri Slaby
2010-10-20 16:13 ` Peter Zijlstra
2010-10-20 17:29 ` Jiri Slaby
2010-10-21 7:34 ` Jiri Slaby
2010-10-21 7:40 ` Peter Zijlstra
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=4CB76A3F.5070903@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome