public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Mark yao <mark.yao@rock-chips.com>,
	David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-rockchip <linux-rockchip@lists.infradead.org>,
	LAKML <linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v3 1/4] drm: Introduce generic probe function for component based masters.
Date: Mon, 09 Nov 2015 20:49:18 +0100	[thread overview]
Message-ID: <2772927.crXiDc9cOV@phil> (raw)
In-Reply-To: <20151109120720.GF963@e106497-lin.cambridge.arm.com>

Hi Liviu,

Am Montag, 9. November 2015, 12:07:20 schrieb Liviu Dudau:
> On Mon, Nov 09, 2015 at 12:03:35PM +0000, Russell King - ARM Linux wrote:
> > On Mon, Nov 09, 2015 at 11:57:27AM +0000, Liviu Dudau wrote:
> > > Meanwhile, what is your suggestion regarding the patchset. I've seen David has
> > > sent Linus a pull request for 4.4-rc1 that includes it. Should we send a
> > > revert for rockchip commit and then patch later the function?
> > 
> > It definitely needs to be fixed, and I'd suggest its early enough in the
> > -rc cycle (which hasn't begun yet) to simply fix drm_of_component_probe()
> > to take two compare functions.
> 
> I still don't have a Rockchip board to test the patch, so I need to find out
> someone willing to test them. Mark?

I of course also have a plethora of rockchip boards, so can test stuff
as well.


Heiko


  reply	other threads:[~2015-11-09 19:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 15:07 [RFC PATCH v3 0/4] drm: Cleanup probe function for component based masters Liviu Dudau
2015-10-19 15:07 ` [RFC PATCH v3 1/4] drm: Introduce generic " Liviu Dudau
2015-10-19 15:14   ` Russell King - ARM Linux
2015-10-20  9:45   ` Eric Anholt
2015-11-09  9:39   ` Mark yao
2015-11-09 10:53     ` Liviu Dudau
2015-11-09 11:20       ` Philipp Zabel
2015-11-09 11:43     ` Russell King - ARM Linux
2015-11-09 11:57       ` Liviu Dudau
2015-11-09 12:03         ` Russell King - ARM Linux
2015-11-09 12:07           ` Liviu Dudau
2015-11-09 19:49             ` Heiko Stuebner [this message]
     [not found]         ` <5641B075.6020602@rock-chips.com>
2015-11-10 10:09           ` Liviu Dudau
2015-11-09 11:15   ` Russell King - ARM Linux
2015-10-19 15:07 ` [RFC PATCH v3 2/4] drm/imx: Convert the probe function to the generic drm_of_component_probe() Liviu Dudau
2015-10-19 15:15   ` Russell King - ARM Linux
2015-10-19 15:07 ` [RFC PATCH v3 3/4] drm/rockchip: " Liviu Dudau
2015-10-19 15:07 ` [RFC PATCH v3 4/4] drm/armada: " Liviu Dudau
2015-10-19 15:17   ` Russell King - ARM Linux
2015-10-19 15:23     ` Liviu Dudau
2015-10-19 22:07   ` kbuild test robot

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=2772927.crXiDc9cOV@phil \
    --to=heiko@sntech.de \
    --cc=Liviu.Dudau@arm.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.yao@rock-chips.com \
    --cc=p.zabel@pengutronix.de \
    /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