From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751133Ab1IUPYU (ORCPT ); Wed, 21 Sep 2011 11:24:20 -0400 Received: from mho-03-ewr.mailhop.org ([204.13.248.66]:44151 "EHLO mho-01-ewr.mailhop.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750751Ab1IUPYS (ORCPT ); Wed, 21 Sep 2011 11:24:18 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 98.234.237.12 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/Ugrx9xTOXujVlBPxcyPZ9 Date: Wed, 21 Sep 2011 08:24:00 -0700 From: Tony Lindgren To: Greg KH Cc: Ohad Ben-Cohen , Andrew Morton , Arnd Bergmann , Russell King , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Linus Walleij , Linus Torvalds , Nicolas Pitre , Thomas Gleixner , Stephen Rothwell , Grant Likely Subject: Re: [PATCH 00/10] hwspinlock-next Message-ID: <20110921152359.GD2937@atomide.com> References: <1315846025-11453-1-git-send-email-ohad@wizery.com> <20110920231340.GT18894@atomide.com> <20110920234515.GA16276@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110920234515.GA16276@kroah.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Greg KH [110921 07:27]: > On Tue, Sep 20, 2011 at 04:13:40PM -0700, Tony Lindgren wrote: > > * Ohad Ben-Cohen [110920 01:34]: > > > On Mon, Sep 12, 2011 at 7:46 PM, Ohad Ben-Cohen wrote: > > > > > > I'm wondering how hwspinlock updates like this should go upstream. > > > > > > The first hwspinlock batch was picked by Tony, because it involved a > > > bulk of OMAP changes. > > > > > > Hwspinlock isn't OMAP-specific anymore though (we gained support for > > > STE's u8500) and the vast majority of changes are in drivers/. We're > > > still very much ARM-related, though this may change too at some point > > > (c6x has a similar "hardware semaphore" peripheral like the u8500 > > > does). > > > > > > Tony, if you're still willing to pick up these updates I'd be happy to > > > send you pull requests of course. > > > > I'd prefer for Greg to take these as these are drivers. > > What, am I the catch-all for drivers these days? > > Oh, right, it looks like I am :) > > > If he's not taking it at this point based on it being ARM only, > > I can take it then. > > Please do, I don't even have the ability to build them here, as I don't > have an arm cross-compiler on this travel laptop. OK so you're off the hook then :) Now we still need to sort out the remaining options posted by Arnd. Tony