From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Inki Dae <inki.dae@samsung.com>, dri-devel@lists.freedesktop.org
Cc: airlied@linux.ie, devicetree@vger.kernel.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
k.kozlowski@samsung.com
Subject: Re: [PATCH v3 1/3] drm/exynos: dp: add of_graph dt binding support for panel
Date: Fri, 4 Dec 2015 09:38:35 -0300 [thread overview]
Message-ID: <5661894B.1090105@osg.samsung.com> (raw)
In-Reply-To: <56615619.2040208@samsung.com>
Hello Inki,
On 12/04/2015 06:00 AM, Inki Dae wrote:
> Hi Javier,
>
> 2015년 12월 03일 22:55에 Javier Martinez Canillas 이(가) 쓴 글:
>> Hello Inki,
>>
>> I found that v2 of this patch is alredy in your exynos-drm for-next branch so
>> so I had to revert it in linux-next to apply this one to test. You shouldn't
>> push patches that were still not reviewed (specially the ones that weren't
>> tested like this one) to your branch that gets pulled by -next. The idea of
>> -next is to have some test coverage but it should be as stable as possible.
>
> exynos-drm/for-next branch is not really for-next branch. This branch is used
Well, it is a for-next branch because is pulled by -next. It is listed in:
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Next/Trees
drm-exynos git git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git#exynos-drm/for-next
> only for integration test. As you know, there are many exynos maintainers
> and they have their own repository. So we would need to test the integration.
Integration testing is of course very needed and linux-next is for that but
what should be tested are the patches that are targeted to mainline.
> For this, exynos-drm/for-next is merged to linux-next not Dave's tree.
> Only exynos-drm-next branch will be merged to Dave's tree so only reviewed and
> tested patches will be merged to exynos-drm-next.
>
In that case, exynos-drm-next is what should be pulled by linux-next, no the
for-next branch. Linux-next is a simulation of what Torvalds would do next
so problems are found earlier, ideally before the patches land into mainline.
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2015-12-04 12:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 9:30 [PATCH 0/3] drm/exynos: dp: consider port node outbound for panel Inki Dae
2015-12-03 9:30 ` [PATCH v3 1/3] drm/exynos: dp: add of_graph dt binding support " Inki Dae
2015-12-03 13:55 ` Javier Martinez Canillas
2015-12-04 9:00 ` Inki Dae
2015-12-04 12:38 ` Javier Martinez Canillas [this message]
2015-12-04 14:57 ` Inki Dae
2015-12-04 16:18 ` Javier Martinez Canillas
2015-12-03 9:30 ` [PATCH v2 2/3] drm/exynos: dp: fix wrong return type Inki Dae
2015-12-03 9:30 ` [PATCH 3/3] dt-bindings: exynos-dp: update ports node binding for panel Inki Dae
2015-12-03 13:29 ` Javier Martinez Canillas
2015-12-04 9:07 ` Inki Dae
2015-12-03 23:38 ` Rob Herring
2015-12-04 9:08 ` Inki Dae
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=5661894B.1090105@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=inki.dae@samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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 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.