From: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
To: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
bcm43xx-dev-tdrK/OAtAx2ELgA04lAiVw@public.gmane.org
Subject: Please pull from my tree
Date: Wed, 6 Sep 2006 22:58:48 +0200 [thread overview]
Message-ID: <200609062258.48696.mb@bu3sch.de> (raw)
Hi John,
Please do
git pull git://bu3sch.de/wireless-dev.git fixes-for-linville
This will pull a ssb fix I forgot to send upstream
via patches.
http://bu3sch.de/git?p=wireless-dev.git;a=commitdiff;h=e29495e14131be28da4fb8bf8a2615fd3f625764
drivers/misc/ssb.c | 29 +++++++++++++-------
drivers/net/wireless/d80211/bcm43xx/bcm43xx_main.c | 6 ++++
include/linux/ssb.h | 15 ++++++++++
3 files changed, 39 insertions(+), 11 deletions(-)
--
Greetings Michael.
reply other threads:[~2006-09-06 20:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200609062258.48696.mb@bu3sch.de \
--to=mb-fseuscv1ubazqb+pc5nmwq@public.gmane.org \
--cc=bcm43xx-dev-tdrK/OAtAx2ELgA04lAiVw@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).