From: Kalle Valo <kvalo@qca.qualcomm.com>
To: David Miller <davem@davemloft.net>
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linville@tuxdriver.com
Subject: Re: linux-next: merge of the wireless-next tree into the net-next tree
Date: Wed, 4 Jan 2012 20:50:19 +0200 [thread overview]
Message-ID: <4F049F6B.3030900@qca.qualcomm.com> (raw)
In-Reply-To: <20120104.132412.1376413566875687968.davem@davemloft.net>
On 01/04/2012 08:24 PM, David Miller wrote:
> From: Kalle Valo <kvalo@qca.qualcomm.com>
> Date: Wed, 4 Jan 2012 10:02:33 +0200
>
>> For a temporary solution I'll send a patch which forces ath6kl to
>> build only as a module and I'll send ath6kl_core.ko patches ASAP
>> after that.
>
> That's not reasonable, fix it properly.
I will, I have the patches almost ready now. Will send them tonight.
Just wanted to send a quick fix first.
Sorry about the whole mess. I was sure that I compile tested the usb
code properly when I added them, but apparently I didn't.
Kalle
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: David Miller <davem@davemloft.net>
Cc: <sfr@canb.auug.org.au>, <netdev@vger.kernel.org>,
<linux-next@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linville@tuxdriver.com>
Subject: Re: linux-next: merge of the wireless-next tree into the net-next tree
Date: Wed, 4 Jan 2012 20:50:19 +0200 [thread overview]
Message-ID: <4F049F6B.3030900@qca.qualcomm.com> (raw)
In-Reply-To: <20120104.132412.1376413566875687968.davem@davemloft.net>
On 01/04/2012 08:24 PM, David Miller wrote:
> From: Kalle Valo <kvalo@qca.qualcomm.com>
> Date: Wed, 4 Jan 2012 10:02:33 +0200
>
>> For a temporary solution I'll send a patch which forces ath6kl to
>> build only as a module and I'll send ath6kl_core.ko patches ASAP
>> after that.
>
> That's not reasonable, fix it properly.
I will, I have the patches almost ready now. Will send them tonight.
Just wanted to send a quick fix first.
Sorry about the whole mess. I was sure that I compile tested the usb
code properly when I added them, but apparently I didn't.
Kalle
next prev parent reply other threads:[~2012-01-04 18:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 23:59 linux-next: merge of the wireless-next tree into the net-next tree Stephen Rothwell
2012-01-03 23:59 ` Stephen Rothwell
2012-01-04 1:27 ` David Miller
2012-01-04 14:02 ` John W. Linville
2012-01-04 18:32 ` David Miller
2012-01-04 8:02 ` Kalle Valo
2012-01-04 8:02 ` Kalle Valo
2012-01-04 18:24 ` David Miller
2012-01-04 18:50 ` Kalle Valo [this message]
2012-01-04 18:50 ` Kalle Valo
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=4F049F6B.3030900@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.