Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752081AbbG0KYE (ORCPT ); Mon, 27 Jul 2015 06:24:04 -0400 Received: from smtprelay2.synopsys.com ([198.182.60.111]:50778 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751217AbbG0KYB convert rfc822-to-8bit (ORCPT ); Mon, 27 Jul 2015 06:24:01 -0400 From: Vineet Gupta To: Kalle Valo , Arend van Spriel CC: Peter Zijlstra , Ingo Molnar , Arnd Bergmann , "linux-arch@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Brett Rudley , "Franky (Zhenhui) Lin" , Hante Meuleman , Pieter-Paul Giesberts , Daniel Kim , "linux-wireless@vger.kernel.org" , "brcm80211-dev-list@broadcom.com" , "netdev@vger.kernel.org" Subject: Re: [PATCH 2/3] brcmfmac: dhd_sdio.c: use existing atomic_or primitive Thread-Topic: [PATCH 2/3] brcmfmac: dhd_sdio.c: use existing atomic_or primitive Thread-Index: AQHQxjKo2kVMLrWKoEqI5eq4rhRpYg== Date: Mon, 27 Jul 2015 10:23:53 +0000 Message-ID: References: <1436429599-10762-1-git-send-email-vgupta@synopsys.com> <1436429599-10762-3-git-send-email-vgupta@synopsys.com> <87twstbi9p.fsf@kamboji.qca.qualcomm.com> <55B2743F.6060304@synopsys.com> <55B4C0A8.9000909@broadcom.com> <871tftc3pw.fsf@kamboji.qca.qualcomm.com> Accept-Language: en-US, en-IN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.12.197.226] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1037 Lines: 21 On Monday 27 July 2015 01:08 PM, Kalle Valo wrote: >>> >> Per last discussion on this topic, Arend wanted to discuss abt this with Hante. >>> >> I'm not taking it anyways so feel free to pick it up if you want ! >> > >> > Well, that was before your "timeline" clarification about the generic >> > function. One what tree is this patch based? > Yeah, if this patch depends on another patch I need to know about it. > Otherwise I might break something when I apply this patch. It was latest linux-next at the time, 4.1-rcx perhaps, don't remember exactly. But it certainly doesn't depend on any new code - the patch simply makes use of an existing API vs. using a local hard coded version of same. Give it a spin off your existing tree - shdn't be too difficult to test I presume. -Vineet -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/