From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] bcm43xx-d80211: fix a sparse warning
Date: Tue, 27 Feb 2007 16:42:04 +0100 [thread overview]
Message-ID: <200702271642.04870.mb@bu3sch.de> (raw)
In-Reply-To: <1172531554.3870.208.camel@johannes.berg>
On Tuesday 27 February 2007 00:12, Johannes Berg wrote:
> This fixes a missing prototype sparse complains about.
Thanks, applied.
--
Greetings Michael.
prev parent reply other threads:[~2007-02-27 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 23:12 [PATCH] bcm43xx-d80211: fix a sparse warning Johannes Berg
2007-02-27 15:42 ` 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=200702271642.04870.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.