mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Daniel Stone <daniel@fooishbar.org>
Cc: Akshay Bhat <akshay.bhat@timesys.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] component: remove device from master match list on failed add
Date: Mon, 15 Feb 2016 16:41:21 +0000	[thread overview]
Message-ID: <20160215164121.GI10826@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAPj87rNHCUv9MND88njdHz-J0hbL1fYJqEzKbVpmvQdcsdUbpQ@mail.gmail.com>

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@timesys.com> 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@timesys.com>
> >
> > 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.

      reply	other threads:[~2016-02-15 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-08 21:12 Daniel Stone
2016-02-12  0:57 ` Akshay Bhat
2016-02-15 16:36   ` Daniel Stone
2016-02-15 16:41     ` Russell King - ARM Linux [this message]

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=20160215164121.GI10826@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=akshay.bhat@timesys.com \
    --cc=daniel@fooishbar.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®