From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751675AbbCJFYI (ORCPT <rfc822;w@1wt.eu>);
	Tue, 10 Mar 2015 01:24:08 -0400
Received: from bhuna.collabora.co.uk ([93.93.135.160]:43200 "EHLO
	bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751187AbbCJFYG (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 10 Mar 2015 01:24:06 -0400
Message-ID: <54FE7FEE.7020607@collabora.co.uk>
Date: Tue, 10 Mar 2015 06:23:58 +0100
From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0
MIME-Version: 1.0
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
References: <1424173109-30347-1-git-send-email-javier.martinez@collabora.co.uk> <7hioehu8cn.fsf@linaro.org> <54F6C746.606@samsung.com> <54F6DD79.9070009@collabora.co.uk> <54F9AC76.1000305@samsung.com> <54F9C29C.7050608@collabora.co.uk> <54FE5BDA.5030707@samsung.com>
In-Reply-To: <54FE5BDA.5030707@samsung.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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