Re: Inconsistent lock state caused by omap_mbox_msg_send() called from tidspbridge

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

 



On Mon, Dec 13, 2010 at 2:49 PM, Ohad Ben-Cohen <ohad@xxxxxxxxxx> wrote:
> On Mon, Dec 13, 2010 at 6:45 PM, Laurent Pinchart
> <laurent.pinchart@xxxxxxxxxxxxxxxx> >> On Sun, Dec 12, 2010 at 4:15
> PM, Ionut Nicu <ionut.nicu@xxxxxxxxxx> wrote:
>>> > I noticed this too, but this patch should fix it:
>>> >
>>> > https://patchwork.kernel.org/patch/365292/
>>>
>>> True. And in this patch the move to spin_lock_bh() is justifiable,
>>> too, since it adds a sending path which is parallel to the mailbox
>>> tasklet.
>>
>> Is this patch set ready for inclusion in the mainline kernel, or does it need
>> to be reworked ?
>
> Better let Hari answer this one.
>

Yes, it is set to go into mainline kernel.


Thank you,
Best regards,
Hari Kanigeri
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux