From: Michael Buesch <mb@bu3sch.de>
To: Jiri Benc <jbenc@suse.cz>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [RFC PATCH] d80211: fix build break from netdev class_device -> device changes
Date: Wed, 21 Feb 2007 18:49:16 +0100 [thread overview]
Message-ID: <200702211849.16990.mb@bu3sch.de> (raw)
In-Reply-To: <20070221184525.4a40779b@griffin.suse.cz>
On Wednesday 21 February 2007 18:45, Jiri Benc wrote:
> Looks correct. Don't know if it's complete, though - I tried to pull
> from Linus but there are many conflicts caused by the ssb code,
Uh, which kind of? If you don't know how to resolve this, let me
resolve it.
--
Greetings Michael.
prev parent reply other threads:[~2007-02-21 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 0:58 [RFC PATCH] d80211: fix build break from netdev class_device -> device changes John W. Linville
2007-02-21 10:45 ` Johannes Berg
2007-02-21 13:32 ` John W. Linville
2007-02-23 14:59 ` [RFC] convert wiphy to struct device Johannes Berg
2007-02-23 20:19 ` Greg KH
2007-02-23 20:33 ` Johannes Berg
2007-02-21 17:45 ` [RFC PATCH] d80211: fix build break from netdev class_device -> device changes Jiri Benc
2007-02-21 17:49 ` Michael Buesch [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=200702211849.16990.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).