From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Inki Dae <inki.dae@samsung.com>
Cc: Kevin Hilman <khilman@linaro.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init
Date: Thu, 20 Nov 2014 15:28:39 +0100 [thread overview]
Message-ID: <546DFA97.1030006@collabora.co.uk> (raw)
In-Reply-To: <546DF598.6030701@samsung.com>
Hello Inki,
On 11/20/2014 03:07 PM, Inki Dae wrote:
> Could you re-base this patch on top of exynos-drm-next? I tried to
> separate sub drivers into independent drivers but it seems that we need
> more times. So I will merge your patch.
>
Sure, I'll rebase on top of exynos-drm-next and re-post so you can apply it.
BTW, it would be great if exynos-drm-next is pulled in linux-next. That is
what most people use to test integration issues so you can catch earlier any
regression that may arise.
You have to email Stephen Rothwell <sfr@canb.auug.org.au> and point to your
tree and branch and he will be able to add it to linux-next.
> Thanks,
> Inki Dae
>
Best regards,
Javier
next prev parent reply other threads:[~2014-11-20 14:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 13:53 [RFC PATCH 1/1] drm/exynos: Move platform drivers registration to module init Javier Martinez Canillas
2014-11-18 18:41 ` Kevin Hilman
2014-11-18 20:28 ` Gustavo Padovan
2014-11-18 22:46 ` Kevin Hilman
2014-11-19 10:09 ` Javier Martinez Canillas
2014-11-19 16:52 ` Javier Martinez Canillas
2014-11-19 19:52 ` Kevin Hilman
2014-11-19 22:29 ` Kevin Hilman
2014-11-20 7:06 ` Vivek Gautam
2014-11-20 7:51 ` Vivek Gautam
2014-11-20 8:45 ` Javier Martinez Canillas
2014-11-20 9:52 ` Vivek Gautam
2014-11-20 14:24 ` Pankaj Dubey
2014-11-20 15:57 ` Paolo Pisati
2014-11-20 16:44 ` Javier Martinez Canillas
2014-11-20 16:41 ` Kevin Hilman
2014-11-20 17:47 ` Javier Martinez Canillas
2014-11-20 18:22 ` Kevin Hilman
2014-11-20 23:49 ` Paolo Pisati
2014-11-21 11:33 ` Andreas Färber
2014-11-21 17:32 ` Ajay kumar
2014-11-21 20:57 ` Javier Martinez Canillas
2014-11-24 10:05 ` Javier Martinez Canillas
2014-11-24 10:36 ` Vivek Gautam
2014-11-24 15:05 ` Andreas Färber
2014-11-25 5:35 ` Ajay kumar
2014-11-20 14:07 ` Inki Dae
2014-11-20 14:28 ` Javier Martinez Canillas [this message]
2014-11-20 15:06 ` Inki Dae
2014-11-20 15:26 ` Javier Martinez Canillas
2014-11-20 17:01 ` Inki Dae
2014-11-21 11:19 ` Javier Martinez Canillas
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=546DFA97.1030006@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-samsung-soc@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