From: Hauke Mehrtens <hauke@hauke-m.de>
To: Florian Fainelli <florian@openwrt.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Julian Calaby" <julian.calaby@gmail.com>,
gregkh@linuxfoundation.org, stern@rowland.harvard.edu,
linux-mips@linux-mips.org, ralf@linux-mips.org, m@bues.ch,
linux-usb@vger.kernel.org, "Rafał Miłecki" <zajec5@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3/7] bcma: scan for extra address space
Date: Mon, 12 Mar 2012 21:47:30 +0100 [thread overview]
Message-ID: <4F5E60E2.3080203@hauke-m.de> (raw)
In-Reply-To: <4F5E395F.9020603@openwrt.org>
On 03/12/2012 06:58 PM, Florian Fainelli wrote:
>
>
> Le 03/12/12 18:41, John W. Linville a écrit :
>> On Mon, Mar 12, 2012 at 12:30:54PM +1100, Julian Calaby wrote:
>>> Hi Hauke,
>>>
>>> On Mon, Mar 12, 2012 at 10:34, Hauke Mehrtens<hauke@hauke-m.de> wrote:
>>
>>>> I will fix this, should I resend the hole series or just this patch?
>>>
>>> I'm not sure the rest of the series made it to linux-wireless, so
>>> maybe you should resend everything.
>>
>> FWIW, this was the only one I saw...
>
> For some reasons I received it from linux-mips-bounces using another
> email account, but only patch 3 CC'd linux-wireless.
Sorry for the confusion.
I didn't send all patches to linux-wireless as the others are just
touching usb and mips. The next round will go completely to linux-wireless.
Hauke
prev parent reply other threads:[~2012-03-12 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1331496505-18697-1-git-send-email-hauke@hauke-m.de>
2012-03-11 20:08 ` [PATCH 3/7] bcma: scan for extra address space Hauke Mehrtens
2012-03-11 21:59 ` Julian Calaby
2012-03-11 23:34 ` Hauke Mehrtens
2012-03-12 1:30 ` Julian Calaby
2012-03-12 17:41 ` John W. Linville
2012-03-12 17:58 ` Florian Fainelli
2012-03-12 20:47 ` Hauke Mehrtens [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=4F5E60E2.3080203@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=florian@openwrt.org \
--cc=gregkh@linuxfoundation.org \
--cc=julian.calaby@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=m@bues.ch \
--cc=ralf@linux-mips.org \
--cc=stern@rowland.harvard.edu \
--cc=zajec5@gmail.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).