From mboxrd@z Thu Jan 1 00:00:00 1970 From: Larry Finger Subject: Re: linux-next: manual merge of the wireless-next tree Date: Mon, 07 Oct 2013 12:16:19 -0500 Message-ID: <5252EC63.9090601@lwfinger.net> References: <1381159127-11067-1-git-send-email-treding@nvidia.com> <1381159127-11067-5-git-send-email-treding@nvidia.com> <5252D7E4.2050509@lwfinger.net> <1381161393.2081.177.camel@joe-AO722> <5252DC9C.8090803@lwfinger.net> <1381162656.2081.179.camel@joe-AO722> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mail-ie0-f171.google.com ([209.85.223.171]:34925 "EHLO mail-ie0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755582Ab3JGRQX (ORCPT ); Mon, 7 Oct 2013 13:16:23 -0400 In-Reply-To: <1381162656.2081.179.camel@joe-AO722> Sender: linux-next-owner@vger.kernel.org List-ID: To: Joe Perches Cc: Thierry Reding , "John W. Linville" , Arend van Spriel , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org On 10/07/2013 11:17 AM, Joe Perches wrote: > > Or maybe John could merge changes from net-next > into wireless-next a bit more often. I'm not sure that John pulls from net-next. My understanding of the work flow is wireless-next => net-next => linux-next => mainline => wireless-next... Larry