From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Ivo van Doorn <IvDoorn@gmail.com>
Subject: Re: [PATCH] rt2x00: Export rt2x00soc_probe from rt2x00soc
Date: Wed, 3 Mar 2010 18:04:53 +0100 [thread overview]
Message-ID: <201003031804.54121.helmut.schaa@googlemail.com> (raw)
In-Reply-To: <14add3d11003030850j2c16a92dsfad2a4a43c4d126c@mail.gmail.com>
Am Mittwoch 03 März 2010 schrieb Gertjan van Wingerde:
> Thanks for doing this. I couldn't test these configurations as I am
> lacking SoC devices.
No problem, I'm just trying to get the driver up on one of these SoC devices.
Not sure how far I'll get :)
Helmut
next prev parent reply other threads:[~2010-03-03 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 16:42 [PATCH] rt2x00: Export rt2x00soc_probe from rt2x00soc Helmut Schaa
2010-03-03 16:50 ` Gertjan van Wingerde
2010-03-03 17:04 ` Helmut Schaa [this message]
2010-03-03 17:08 ` Gertjan van Wingerde
2010-03-03 19:09 ` Helmut Schaa
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=201003031804.54121.helmut.schaa@googlemail.com \
--to=helmut.schaa@googlemail.com \
--cc=IvDoorn@gmail.com \
--cc=gwingerde@gmail.com \
--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).