From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: Re: Please pull 'upstream' branch of wireless-2.6
Date: Tue, 26 Dec 2006 16:39:38 -0500
Message-ID: <4591969A.1040403@garzik.org>
References: <20061221030340.GA9277@tuxdriver.com> <20061221030503.GB9277@tuxdriver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org
Return-path: <netdev-owner@vger.kernel.org>
Received: from srv5.dvmed.net ([207.36.208.214]:41538 "EHLO mail.dvmed.net"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932785AbWLZVjk (ORCPT <rfc822;netdev@vger.kernel.org>);
	Tue, 26 Dec 2006 16:39:40 -0500
To: "John W. Linville" <linville@tuxdriver.com>
In-Reply-To: <20061221030503.GB9277@tuxdriver.com>
Sender: netdev-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

John W. Linville wrote:
> The following changes since commit 0c234ae655a45ac3ee53a25b2e56e9bb6c27d71d:
>   Ulrich Kunitz (1):
>         ieee80211softmac: Fix mutex_lock at exit of ieee80211_softmac_get_genie
> 
> are found in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream
> 
> Roy Marples (1):
>       prism54: set carrier flags correctly

Why is this not #upstream-fixes material?  What's the impact?

	Jeff