From: Seung-Woo Kim <sw0312.kim@samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: "linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Kyungmin Park <kyungmin.park@samsung.com>,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 2/2] drm/exynos: Fix build after removal of DRM_WAKUP
Date: Wed, 08 Jan 2014 21:15:53 +0900 [thread overview]
Message-ID: <52CD4179.2050108@samsung.com> (raw)
In-Reply-To: <20140108120341.GQ31886@sirena.org.uk>
Hello,
On 2014년 01월 08일 21:03, Mark Brown wrote:
> On Wed, Jan 08, 2014 at 10:15:25AM +0900, Inki Dae wrote:
>> 2014/1/8 Daniel Vetter <daniel@ffwll.ch>:
>
>>> Oops, looks like something slipped past between me making the patches and
>>> them getting merged. Thanks for taking care of this. Both patches are
>
>> These patches already were posted by Seung-Woo link below, and I
>> merged already them to exynos-drm-next.
>> http://www.spinics.net/lists/dri-devel/msg50921.html
>
> Are you sure? I still need those patches in -next as of today.
>
Yes, at least for exynos-drm-next tree of Inki. Inki sent pull request
including my patch yesterday.
Best Regards,
- Seung-Woo Kim
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2014-01-08 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 13:59 [PATCH 1/2] drm/exynos: Fix build after removal of DRM_HZ Mark Brown
2014-01-07 13:59 ` [PATCH 2/2] drm/exynos: Fix build after removal of DRM_WAKUP Mark Brown
2014-01-07 16:14 ` Daniel Vetter
2014-01-08 1:15 ` Inki Dae
2014-01-08 12:03 ` Mark Brown
2014-01-08 12:15 ` Seung-Woo Kim [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=52CD4179.2050108@samsung.com \
--to=sw0312.kim@samsung.com \
--cc=broonie@kernel.org \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kyungmin.park@samsung.com \
--cc=linaro-kernel@lists.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 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.