mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Liviu Dudau <Liviu.Dudau@arm.com>
To: Mark yao <mark.yao@rock-chips.com>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-rockchip <linux-rockchip@lists.infradead.org>,
	LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH v3 1/4] drm: Introduce generic probe function for component based masters.
Date: Tue, 10 Nov 2015 10:09:09 +0000	[thread overview]
Message-ID: <20151110100909.GI963@e106497-lin.cambridge.arm.com> (raw)
In-Reply-To: <5641B075.6020602@rock-chips.com>

On Tue, Nov 10, 2015 at 04:53:09PM +0800, Mark yao wrote:
>    On 2015年11月09日 19:57, 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?
> 
>    Hi Liviu
>        I had sent a patch to revert this rockchip commit, verfied rockchip drm works. So we can do the fix later.

Yeah, and I'm thinking about ACK-ing it. On one hand I would like to
have this fixed, on the other hand I don't want the rockchip platform
to be broken. But looking at the rest of the changes I need to do it
doesn't feel right to make you wait for them.

Best regards,
Liviu

> 
>    Thanks all the same. :-)
> 
>    -- Mark Yao

> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel


-- 
====================
| I would like to |
| fix the world,  |
| but they're not |
| giving me the   |
 \ source code!  /
  ---------------
    ¯\_(ツ)_/¯

  parent reply	other threads:[~2015-11-10 10:09 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 " 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
     [not found]         ` <5641B075.6020602@rock-chips.com>
2015-11-10 10:09           ` Liviu Dudau [this message]
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=20151110100909.GI963@e106497-lin.cambridge.arm.com \
    --to=liviu.dudau@arm.com \
    --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 \
    /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®