From: "J.R. Mauro" <jrm8005@gmail.com>
To: "Randy Dunlap" <randy.dunlap@oracle.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
gregkh <greg@kroah.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 14 (staging/agnx/)
Date: Fri, 14 Nov 2008 16:28:13 -0500 [thread overview]
Message-ID: <3aaafc130811141328n61b3fe43wd838140ef350f219@mail.gmail.com> (raw)
In-Reply-To: <20081114111517.c2d9b2f9.randy.dunlap@oracle.com>
On Fri, Nov 14, 2008 at 2:15 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Fri, 14 Nov 2008 18:40:21 +1100 Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 20081113:
>>
>> New tree:
>> staging
>
>
> drivers/staging/agnx/pci.c:327: error: 'struct ieee80211_if_conf' has no member named 'ssid_len'
> drivers/staging/agnx/pci.c:328: error: 'struct ieee80211_if_conf' has no member named 'ssid'
> drivers/staging/agnx/pci.c:328: error: 'struct ieee80211_if_conf' has no member named 'ssid_len'
> drivers/staging/agnx/pci.c:329: error: 'struct ieee80211_if_conf' has no member named 'ssid'
> drivers/staging/agnx/pci.c:329: error: 'struct ieee80211_if_conf' has no member named 'ssid_len'
> drivers/staging/agnx/pci.c:330: error: 'struct ieee80211_if_conf' has no member named 'ssid_len'
> drivers/staging/agnx/pci.c:331: error: 'struct ieee80211_if_conf' has no member named 'ssid_len'
> drivers/staging/agnx/pci.c:331: error: 'struct ieee80211_if_conf' has no member named 'ssid_len'
> drivers/staging/agnx/pci.c:331: error: 'struct ieee80211_if_conf' has no member named 'ssid'
> drivers/staging/agnx/pci.c:331: error: 'struct ieee80211_if_conf' has no member named 'ssid
It looks like commit 41bb73eeac5ff5fb217257ba33b654747b3abf11 removed
these members from ieee80211_if_conf under the assumption that no
drivers used them.
>
> config attached.
>
> ---
> ~Randy
>
prev parent reply other threads:[~2008-11-14 21:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 7:40 linux-next: Tree for November 14 Stephen Rothwell
2008-11-14 17:52 ` linux-next: Tree for November 14 (staging) Randy Dunlap
2008-11-14 18:11 ` Greg KH
2008-11-14 18:22 ` Randy Dunlap
2008-11-15 1:01 ` J.R. Mauro
2008-11-25 5:50 ` Greg KH
2008-11-14 18:11 ` linux-next: Tree for November 14 (staging#2) Randy Dunlap
2008-11-14 22:13 ` J.R. Mauro
2008-11-14 22:57 ` Randy Dunlap
2008-11-14 23:53 ` J.R. Mauro
2008-11-14 18:28 ` linux-next: Tree for November 14 (staging/meilhaus/) Randy Dunlap
2008-11-14 19:13 ` linux-next: Tree for November 14 (staging/meilhaus/ more) Randy Dunlap
2008-11-14 19:15 ` linux-next: Tree for November 14 (staging/agnx/) Randy Dunlap
2008-11-14 21:28 ` J.R. Mauro [this message]
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=3aaafc130811141328n61b3fe43wd838140ef350f219@mail.gmail.com \
--to=jrm8005@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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
all inboxes | Powered by JetHome®