On Wednesday 21 September 2011, Tony Lindgren wrote:
* Ohad Ben-Cohen o...@wizery.com [110920 01:34]:
On Mon, Sep 12, 2011 at 7:46 PM, Ohad Ben-Cohen o...@wizery.com wrote:
I'm wondering how hwspinlock updates like this should go upstream.
The first hwspinlock batch was picked by
On Tue, Sep 20, 2011 at 04:13:40PM -0700, Tony Lindgren wrote:
* Ohad Ben-Cohen o...@wizery.com [110920 01:34]:
On Mon, Sep 12, 2011 at 7:46 PM, Ohad Ben-Cohen o...@wizery.com wrote:
I'm wondering how hwspinlock updates like this should go upstream.
The first hwspinlock batch was
* Greg KH g...@kroah.com [110921 07:27]:
On Tue, Sep 20, 2011 at 04:13:40PM -0700, Tony Lindgren wrote:
* Ohad Ben-Cohen o...@wizery.com [110920 01:34]:
On Mon, Sep 12, 2011 at 7:46 PM, Ohad Ben-Cohen o...@wizery.com wrote:
I'm wondering how hwspinlock updates like this should go
* Arnd Bergmann a...@arndb.de [110921 06:39]:
On Wednesday 21 September 2011, Tony Lindgren wrote:
* Ohad Ben-Cohen o...@wizery.com [110920 01:34]:
On Mon, Sep 12, 2011 at 7:46 PM, Ohad Ben-Cohen o...@wizery.com wrote:
I'm wondering how hwspinlock updates like this should go upstream.
On Wed, Sep 21, 2011 at 4:12 PM, Arnd Bergmann a...@arndb.de wrote:
My feeling is that it would be best for Ohad to send these directly
to Linus, since it's basically a standalone subsystem and he's listed
as the maintainer (well, after this series at least).
I agree. That's the path of least
On Wed, Sep 21, 2011 at 6:28 PM, Tony Lindgren t...@atomide.com wrote:
Ohad can you please try this first? Just please make sure your patches are
first in next tree before sending in the pull request.
Sure thing.
Stephen, I'll send you the location of my tree in a few.
Thanks,
Ohad.
--
To
On Wed, Sep 21, 2011 at 6:56 PM, Ohad Ben-Cohen o...@wizery.com wrote:
On Wed, Sep 21, 2011 at 6:28 PM, Tony Lindgren t...@atomide.com wrote:
Ohad can you please try this first? Just please make sure your patches are
first in next tree before sending in the pull request.
Sure thing.
* Ohad Ben-Cohen o...@wizery.com [110921 08:34]:
On Wed, Sep 21, 2011 at 6:56 PM, Ohad Ben-Cohen o...@wizery.com wrote:
On Wed, Sep 21, 2011 at 6:28 PM, Tony Lindgren t...@atomide.com wrote:
Ohad can you please try this first? Just please make sure your patches are
first in next tree before
On Wed, Sep 21, 2011 at 7:14 PM, Tony Lindgren t...@atomide.com wrote:
OK acked the related patch.
Thanks!
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Wednesday 21 September 2011, Linus Walleij wrote:
On Wed, Sep 21, 2011 at 4:12 PM, Arnd Bergmann a...@arndb.de wrote:
My feeling is that it would be best for Ohad to send these directly
to Linus, since it's basically a standalone subsystem and he's listed
as the maintainer (well, after
On Mon, Sep 12, 2011 at 7:46 PM, Ohad Ben-Cohen o...@wizery.com wrote:
This series includes a new u8500 hwspinlock driver from Mathieu,
a core fix from Juan and several other cleanups/fixes
(some of which were reported by Arnd while reviewing Mathieu's
driver).
...
* Ohad Ben-Cohen o...@wizery.com [110920 01:34]:
On Mon, Sep 12, 2011 at 7:46 PM, Ohad Ben-Cohen o...@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.
This series includes a new u8500 hwspinlock driver from Mathieu,
a core fix from Juan and several other cleanups/fixes
(some of which were reported by Arnd while reviewing Mathieu's
driver).
Maybe the most notable core change is the move to registering
a bank of hwspinlocks in a single API call,
13 matches
Mail list logo