Re: [PATCH] mmc: mmci: Do not release spinlock in request_end

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 14, 2011 at 09:51:44AM +0200, Ulf Hansson wrote:
> Russell King - ARM Linux wrote:
>> In that case, how can I take the patch to mmci if it depends on something
>> in another tree?
>>
>
> I don't know. But how do you update your tree from next normally?

I don't - no one in their right mind does.  linux-next is not a tree
which should ever be pulled into any other git tree to base work upon
- it's completely unstable and you can't rely on any commit in there
remaining.  The merge commits between each tree are also specific to
linux-next only.

Linus will also refuse to pull any tree which has linux-next merged
into it.

> I believe the problem is more related to that the mmc-next tree is now on  
> a temporary git.

Where a tree is hosted has no influence on whether its 'temporary' or
not.

> If you do not update your tree how shall we be able to  
> continue with integration of new patches that depends on mmc patches  
> from "next"?

That's what I'm saying - I can't take the patch as it introduces bugs
if I do.  It's better to either wait until after the next merge window,
or we have to sort out merging it via the mmc tree instead.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux