Return-path: Received: from mga06.intel.com ([134.134.136.31]:34025 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S939360AbeE1OuD (ORCPT ); Mon, 28 May 2018 10:50:03 -0400 Date: Mon, 28 May 2018 16:50:00 +0200 From: Samuel Ortiz To: Daniel Mack Cc: davem@davemloft.net, linux-wireless@vger.kernel.org Subject: Re: [PATCH 1/2] NFC: st95hf: initialize semaphore and mutex earlier Message-ID: <20180528145000.GA11829@zurbaran.ger.intel.com> (sfid-20180528_165119_633920_CA47A120) References: <20180516133247.25986-1-daniel@zonque.org> <6eed2f2f-b3cc-0582-220c-e4ccd2175fd7@zonque.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <6eed2f2f-b3cc-0582-220c-e4ccd2175fd7@zonque.org> Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Daniel, On Mon, May 28, 2018 at 04:35:15PM +0200, Daniel Mack wrote: > On Wednesday, May 16, 2018 03:32 PM, Daniel Mack wrote: > > 'rm_lock' and 'exchange_lock' need to be ready before the IRQ handler has a > > chance to fire. > > > > This fixes the oops below. > > Nobody seems to be interested in these. Davem, can you take them through > your tree or is there anyone else I can ping? I'm going to gather all pending NFC patches this week, including this one. They will land in either the nfc-next or nfc-fixes tree. Cheers, Samuel.