From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John Linville <linville@tuxdriver.com>,
Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ssb: Fix compilation errors in ssb
Date: Fri, 16 Nov 2007 11:30:46 +0100 [thread overview]
Message-ID: <200711161130.46770.mb@bu3sch.de> (raw)
In-Reply-To: <473d3d37.IWXGkSribrkSiHBl%Larry.Finger@lwfinger.net>
On Friday 16 November 2007 07:48:23 Larry Finger wrote:
> Recent changes in ssb sprom handling break compilation. These two patches
> fix the problem.
>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> ---
>
> John,
>
> These two changes should be applied to the everything branch of wireless-2.6
> ASAP. Sorry about the mixup - I have no idea what happened.
are your sprom r4 changes already applied? I didn't test that in the b44, yet.
--
Greetings Michael.
next prev parent reply other threads:[~2007-11-16 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 6:48 [PATCH] ssb: Fix compilation errors in ssb Larry Finger
2007-11-16 10:30 ` Michael Buesch [this message]
2007-11-16 14:21 ` Larry Finger
2007-11-16 14:56 ` John W. Linville
2007-11-16 21:53 ` Michael Buesch
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=200711161130.46770.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=Larry.Finger@lwfinger.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).