From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from s3.sipsolutions.net ([144.76.43.152]:38596 "EHLO
	sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753659Ab3FKSSh (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Tue, 11 Jun 2013 14:18:37 -0400
Message-ID: <1370974699.8356.57.camel@jlt4.sipsolutions.net> (sfid-20130611_201840_701651_1181262C)
Subject: Re: pull-request: iwlwifi-next 2013-06-11
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Date: Tue, 11 Jun 2013 20:18:19 +0200
In-Reply-To: <1370974531.8356.56.camel@jlt4.sipsolutions.net> (sfid-20130611_201543_141311_7A590D93)
References: <1370974531.8356.56.camel@jlt4.sipsolutions.net>
	 (sfid-20130611_201543_141311_7A590D93)
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

On Tue, 2013-06-11 at 20:15 +0200, Johannes Berg wrote:
> Hi,
> 
> For iwlwifi-next I only have a few cleanups:

I was wondering while writing this ... but didn't realize quickly enough
I'd applied a few patches to the wrong tree :(

Sorry about that, new one coming!

johannes