All of lore.kernel.org
 help / color / mirror / Atom feed
From: Inki Dae <inki.dae@samsung.com>
To: Emil Velikov <emil.l.velikov@gmail.com>,
	Archit Taneja <architt@codeaurora.org>
Cc: "Vetter, Daniel" <daniel.vetter@intel.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 12/14] drm/exynos: mic: clean up drm_bridge_add call
Date: Fri, 18 Aug 2017 17:04:37 +0900	[thread overview]
Message-ID: <59969F95.1020803@samsung.com> (raw)
In-Reply-To: <CACvgo51t-WrV03hEsWGkGDqJQddUJyiH9TduaBd74o3qWBgh_Q@mail.gmail.com>



2017년 07월 05일 20:12에 Emil Velikov 이(가) 쓴 글:
> On 5 July 2017 at 10:14, Archit Taneja <architt@codeaurora.org> wrote:
>>
>>
>> On 07/05/2017 02:35 PM, Inki Dae wrote:
>>>
>>>
>>>
>>> 2017년 07월 05일 18:00에 Archit Taneja 이(가) 쓴 글:
>>>>
>>>>
>>>>
>>>> On 07/03/2017 02:12 PM, Inki Dae wrote:
>>>>>
>>>>> This patch removes unnecessary checking of return value.
>>>>>
>>>>> Ps. this patch depends on below one,
>>>>>      http://www.spinics.net/lists/dri-devel/msg145687.html
>>>>
>>>>
>>>> Will this one^ go via the exynos pull req or drm-misc? If there won't
>>>> be any conflicts, we could get both the patches through drm-misc to
>>>> keep things simple.
>>>
>>>
>>> exynos pull it would be better. I will pick this up. :)
>>
>>
>> If patch # 1/14 goes through drm-misc, and the exynos patch goes through
>> exynos pull, the drm-misc branch would break. That's the reason I
>> preferred the exynos patches to go via misc.
>>
> As mentioned in 1/14:
> 
> If 1/14 is applied before the rest of the series all the drivers
> (addressed with 2-14) will fail to build.
> I think...

Indeed. :)

Thanks,
Inki Dae

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

  parent reply	other threads:[~2017-08-18  8:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170703084232epcas1p4edf515b3b0f22e11ef85eaedccebf956@epcas1p4.samsung.com>
2017-07-03  8:42 ` [PATCH 00/14] clean up drm_bridge_add Inki Dae
2017-07-03  8:42   ` [PATCH 01/14] drm/bridge: change return type of drm_bridge_add function Inki Dae
2017-07-03  9:56     ` Emil Velikov
2017-07-03  8:42   ` [PATCH 02/14] drm/bridge: adv7511: clean up drm_bridge_add call Inki Dae
2017-07-03  8:42   ` [PATCH 03/14] drm/bridge: analogix-anx78xx: " Inki Dae
2017-07-03  8:42   ` [PATCH 04/14] drm/bridge: vga-dac: " Inki Dae
2017-07-03  8:42   ` [PATCH 05/14] drm/bridge: nxp-ptn3460: " Inki Dae
2017-07-03  8:42   ` [PATCH 06/14] drm/bridge: panel: " Inki Dae
2017-07-03  8:42   ` [PATCH 07/14] drm/bridge: ps8622: " Inki Dae
2017-07-03  8:42   ` [PATCH 08/14] drm/bridge: sii902x: " Inki Dae
2017-07-03  8:42   ` [PATCH 09/14] drm/bridge: synopsys: dw-hdmi: " Inki Dae
2017-07-03  8:42   ` [PATCH 10/14] drm/bridge: tc358767: " Inki Dae
2017-07-03  8:42   ` [PATCH 11/14] drm/bridge: ti-tfp410: " Inki Dae
2017-07-03  8:42   ` [PATCH 12/14] drm/exynos: mic: " Inki Dae
2017-07-05  9:00     ` Archit Taneja
2017-07-05  9:05       ` Inki Dae
2017-07-05  9:14         ` Archit Taneja
2017-07-05 11:12           ` Emil Velikov
2017-07-06  7:59             ` Archit Taneja
2017-08-18  8:04             ` Inki Dae [this message]
2017-08-18  8:03           ` Inki Dae
2017-08-18  8:01     ` Inki Dae
2017-07-03  8:42   ` [PATCH 13/14] drm/mediatek: hdmi: " Inki Dae
2017-07-05  9:01     ` Archit Taneja
2017-08-18  8:54       ` Daniel Vetter
2017-08-18 13:03         ` CK Hu
2017-07-03  8:42   ` [PATCH 14/14] drm/sti: sti_vdo: " Inki Dae
2017-08-18 15:15     ` Sean Paul
2017-07-06  8:58   ` [PATCH 00/14] clean up drm_bridge_add Archit Taneja
2017-08-22  5:14     ` Inki Dae
2017-08-07 22:55   ` Inki Dae
2017-08-08  3:21     ` Archit Taneja
2017-08-22  5:07       ` Archit Taneja
2017-08-18  7:42     ` 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=59969F95.1020803@samsung.com \
    --to=inki.dae@samsung.com \
    --cc=architt@codeaurora.org \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.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 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.