From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Inki Dae <inki.dae@samsung.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Kevin Hilman <khilman@kernel.org>, Kukjin Kim <kgene@kernel.org>,
Olof Johansson <olof@lixom.net>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Andreas Faerber <afaerber@suse.de>,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
tyler.baker@linaro.org, Andrzej Hajda <a.hajda@samsung.com>,
Inki Dae <daeinki@gmail.com>,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: Re: [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support
Date: Tue, 10 Mar 2015 06:23:58 +0100 [thread overview]
Message-ID: <54FE7FEE.7020607@collabora.co.uk> (raw)
In-Reply-To: <54FE5BDA.5030707@samsung.com>
Hello Inki,
On 03/10/2015 03:50 AM, Inki Dae wrote:
> On 2015년 03월 07일 00:07, Javier Martinez Canillas wrote:
>>>>
>>>> Another thing that may be useful to detect these issues early is to have
>>>> exynos-drm-next be pulled by linux-next since otherwise the integration
>>>> is not tested until the changes are picked by the DRM maintainer.
>>>>
>>
>> I know that I may sound like a broken record but could you please make
>> sure that your tree is included in linux-next?
>
> Got it. I got several requests before. I have created a new branch -
> exynos-drm/for-next - based on top of drm-next, which would have same
> patch set as existing exynos-drm-next.
>
> I will request Stephen Rothwell to merge remote-tracking branch,
> 'exynos-drm/for-next'.
>
Great new, thanks a lot.
> Thanks,
> Inki Dae
>
Best regards,
Javier
prev parent reply other threads:[~2015-03-10 5:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 11:38 [PATCH 1/1] ARM: exynos_defconfig: Disable IOMMU support Javier Martinez Canillas
2015-02-17 12:20 ` Krzysztof Kozlowski
2015-02-17 12:56 ` Javier Martinez Canillas
2015-02-17 13:08 ` Krzysztof Kozlowski
2015-02-17 12:52 ` Marek Szyprowski
2015-02-27 6:20 ` Javier Martinez Canillas
2015-03-02 19:43 ` Kukjin Kim
2015-03-03 7:01 ` Javier Martinez Canillas
2015-03-03 20:36 ` Kevin Hilman
2015-03-04 8:50 ` Marek Szyprowski
2015-03-04 10:24 ` Javier Martinez Canillas
2015-03-04 17:39 ` Kevin Hilman
2015-03-06 13:32 ` Inki Dae
2015-03-06 15:07 ` Javier Martinez Canillas
2015-03-10 2:50 ` Inki Dae
2015-03-10 5:23 ` Javier Martinez Canillas [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=54FE7FEE.7020607@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=a.hajda@samsung.com \
--cc=afaerber@suse.de \
--cc=daeinki@gmail.com \
--cc=gustavo.padovan@collabora.co.uk \
--cc=inki.dae@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=olof@lixom.net \
--cc=tyler.baker@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.