Re: [PATCH] component: remove device from master match list on failed add

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

 



On Mon, Feb 15, 2016 at 04:36:55PM +0000, Daniel Stone wrote:
> Russell,
> 
> On 12 February 2016 at 00:57, Akshay Bhat <akshay.bhat@xxxxxxxxxxx> wrote:
> > Daniel Stone <daniels <at> collabora.com> writes:
> >> Fixes: ffc30b74fd6d01588bd3fdebc3b1acc0857e6fc8
> >> Signed-off-by: Daniel Stone <daniels <at> collabora.com>
> >
> > Tested-by: Akshay Bhat <akshay.bhat@xxxxxxxxxxx>
> >
> > Tested on imx6 processor based board where re-probe was broken after a
> > probe deferral.
> 
> One-week ping; this breaks quite a few drivers, even despite
> 57480484f9 already being present. Another option could just be to
> revert the original match-array commit (and the subsequent two fixups)
> until you can work out a fix.

I assume you haven't checked before sending out reminder emails...
it's in -rc4, and it's been in linux-next since last Thursday.

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel




[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux