From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S933900AbcKIPGy (ORCPT <rfc822;w@1wt.eu>);
        Wed, 9 Nov 2016 10:06:54 -0500
Received: from mout.kundenserver.de ([212.227.17.10]:56709 "EHLO
        mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932705AbcKIPGu (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 9 Nov 2016 10:06:50 -0500
From: Arnd Bergmann <arnd@arndb.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Kalle Valo <kvalo@codeaurora.org>,
        Stanislav Yakovlev <stas.yakovlev@gmail.com>, Jouni Malinen <j@w1.fi>,
        "David S. Miller" <davem@davemloft.net>,
        linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wireless: fix bogus maybe-uninitialized warning
Date: Wed, 09 Nov 2016 16:06:32 +0100
Message-ID: <2654653.cBclyC49py@wuerfel>
User-Agent: KMail/5.1.3 (Linux/4.4.0-34-generic; KDE/5.18.0; x86_64; ; )
In-Reply-To: <1478679046.4345.1.camel@sipsolutions.net>
References: <20161024153918.2810634-1-arnd@arndb.de> <87mvh9qwhi.fsf@purkki.adurom.net> <1478679046.4345.1.camel@sipsolutions.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:k1EE1iCVfmSC81J1RwouXRx1RYu0IAX7+6G/W0lxevPnIa9D3Bv
 77bc+pDUA9yrGPFAOOYa9sV6wKUY2hZb/83f2xbHfVfdT4pEjivbzg7o0UJV2JvvGEZZo6l
 LEkY0h9lITYVHPK4gjfSsTeNScKBc0ggfgFrsUDfObnkQiqI5p8BE4qeL0IFvsXSk+3qk/o
 CVuWcqoYf/jfKRmURJQ8w==
X-UI-Out-Filterresults: notjunk:1;V01:K0:RcTbWKq8jcU=:Ci19embHeYkd2gTCCApnzo
 BzqcuXRRfEPbC9R/iD3E+XKQCRVt4kuTm48CnfEMrwhGStxTZb+IZ7SUUbPBeeGAgrDuEN7dP
 b0TZCGj9HutJUkB9OdNg2W6F0Qt07O3HzzalRKqT+ZQfDKo0NkgwATVylCKfhyDLeET4VPaiq
 gNMj68Ou2EgSDE29nGBib8xxw79fikUkEa0bErfNsM/P8R5A4m8z3AIWGLk37Pr5L1PkViVR6
 CU76IEuEoSJXGTq+AZarTldYcUaOuNnMQD5rSYiJCB8c5mfpBwu1qVI4UlYq1RN6xcRwZ47xn
 t4wnrJNyNr1u+BiGYtgJJ5Iqk+h+POkXn6quKV2On9h7gktGVfM0HmSlIOFxzMlCX4Sl6Ckq+
 Uwi5IEYN7dlDlS+Lfj+SSHrm/RK2DiuG06qHaroY37B/GFztIdHurZquWugFYKCJLUDTQ5oNp
 lqeO9wkDWBmQC7OXWlg05+5reUG7shcYh6xwUp1cb1PP973Vqi6lxmmdkjuRjMbxI6TY2VIur
 rR+2JQSlJGkkqTQcq5optgH5fTvS90og1C3buXfwx/3E561U/R9BdO0HqWLYeo4sdCwF/qxQz
 ksXFu1a6yEoyjdlnTESYm4DfzXb4A8iTE0iYnmUGT2v8BZ3vQhcD+nUn83IOnQOyR99lWYnMO
 S2R/oIAHEqvFvH5ZRkIrex+X6HR3PyB2pL1xlT5Zvu6zNO8cfdzPhSJs6L9EhS63sItqnE+jw
 POHFYV0MAUspUOzU
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wednesday, November 9, 2016 9:10:46 AM CET Johannes Berg wrote:
> 
> > Ideally we prefer that drivers/net/wireless and net/wireless changes
> > are
> > split into different patches as they get applied to different trees.

Ok, good to know. I had split out the drivers/staging changes, but
wasn't sure about the granularity you'd want here.

> > Johannes, is it ok if I take this change through my tree this time?

> Sure, please do, thanks.
> 
> (I don't particularly care about the lib80211 stuff anyway)

Thanks!

	Arnd