From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/10] hwspinlock-next
Date: Wed, 21 Sep 2011 08:24:00 -0700 [thread overview]
Message-ID: <20110921152359.GD2937@atomide.com> (raw)
In-Reply-To: <20110920234515.GA16276@kroah.com>
* Greg KH <greg@kroah.com> [110921 07:27]:
> On Tue, Sep 20, 2011 at 04:13:40PM -0700, Tony Lindgren wrote:
> > * Ohad Ben-Cohen <ohad@wizery.com> [110920 01:34]:
> > > On Mon, Sep 12, 2011 at 7:46 PM, Ohad Ben-Cohen <ohad@wizery.com> 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
next prev parent reply other threads:[~2011-09-21 15:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 16:46 [PATCH 00/10] hwspinlock-next Ohad Ben-Cohen
2011-09-12 16:46 ` [PATCH 01/10] hwspinlock/core: simplify Kconfig Ohad Ben-Cohen
2011-09-12 16:46 ` [PATCH 02/10] hwspinlock/core: simplify 'owner' handling Ohad Ben-Cohen
2011-09-12 16:46 ` [PATCH 03/10] hwspinlock/omap: simplify allocation scheme Ohad Ben-Cohen
2011-09-12 16:46 ` [PATCH 04/10] hwspinlock/core/omap: fix id issues on multiple hwspinlock devices Ohad Ben-Cohen
2011-09-21 16:14 ` Tony Lindgren
2011-09-12 16:47 ` [PATCH 05/10] hwspinlock/core: use a mutex to protect the radix tree Ohad Ben-Cohen
2011-09-12 16:47 ` [PATCH 06/10] hwspinlock/core: remove stubs for register/unregister Ohad Ben-Cohen
2011-09-12 16:47 ` [PATCH 07/10] hwspinlock/core: register a bank of hwspinlocks in a single API call Ohad Ben-Cohen
2011-09-12 16:47 ` [PATCH 08/10] hwspinlock/u8500: add hwspinlock driver Ohad Ben-Cohen
2011-09-12 16:47 ` [PATCH 09/10] hwspinlock/omap: omap_hwspinlock_remove should be __devexit Ohad Ben-Cohen
2011-09-12 16:47 ` [PATCH 10/10] hwspinlock: add MAINTAINERS entries Ohad Ben-Cohen
2011-09-12 16:58 ` Joe Perches
2011-09-12 17:01 ` Ohad Ben-Cohen
2011-09-20 9:07 ` [PATCH 00/10] hwspinlock-next Ohad Ben-Cohen
2011-09-20 23:13 ` Tony Lindgren
2011-09-20 23:45 ` Greg KH
2011-09-21 15:24 ` Tony Lindgren [this message]
2011-09-21 14:12 ` Arnd Bergmann
2011-09-21 15:28 ` Tony Lindgren
2011-09-21 15:56 ` Ohad Ben-Cohen
2011-09-21 16:07 ` Ohad Ben-Cohen
2011-09-21 16:14 ` Tony Lindgren
2011-09-21 16:16 ` Ohad Ben-Cohen
2011-09-21 15:53 ` Linus Walleij
2011-09-21 16:21 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110921152359.GD2937@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).