Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:50188 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753081AbeB0NWr (ORCPT ); Tue, 27 Feb 2018 08:22:47 -0500 From: Kalle Valo To: Sebastian Gottschall Cc: "linux-firmware\@kernel.org" , "linux-wireless\@vger.kernel.org" , "ath10k\@lists.infradead.org" Subject: Re: [PULL] ath10k firmware 20180219 References: <87y3jlxq0k.fsf@kamboji.qca.qualcomm.com> <0e9db63d-41e9-eeb3-00d1-73b20df4bb3f@dd-wrt.com> <87606ju7ae.fsf@kamboji.qca.qualcomm.com> <150ef362-418d-e571-a95d-b1fa7d6db14c@dd-wrt.com> Date: Tue, 27 Feb 2018 15:22:43 +0200 In-Reply-To: <150ef362-418d-e571-a95d-b1fa7d6db14c@dd-wrt.com> (Sebastian Gottschall's message of "Tue, 27 Feb 2018 10:05:38 +0100") Message-ID: <87woyysh24.fsf@kamboji.qca.qualcomm.com> (sfid-20180227_142350_029036_57A180BA) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-wireless-owner@vger.kernel.org List-ID: Sebastian Gottschall writes: > what about this? It would be a lot easier if you could start a new thread (with a proper subject) on ath10k@lists.infradead.org for each firmware problem you see, instead of hijacking this thread. And no need to CC linux-firmware maintainers either. -- Kalle Valo