[PATCH v4] drm/exynos: prepare FIMD clocks

[Tomasz Figa]

Hi Inki,

On Sunday 21 of April 2013 23:05:45 Inki Dae wrote:
> 2013/4/21 Tomasz Figa <tomasz.figa at gmail.com>
> 
> > On Sunday 21 of April 2013 13:23:10 Viresh Kumar wrote:
> > > On 20 April 2013 20:56, Inki Dae <inki.dae at samsung.com> wrote:
> > > > Sorry for being late. I think clk_prepare/unprepare are nothing to
> > > > do
> > > > yet in case of Exynos but those might be used for in the future so
> > > > your patch looks good to me as is.
> > > > 
> > > > Applied. :)
> > 
> > Hmm. Now, after searching for this thread in dri-devel archives, I'm
> > wondering why I haven't received some of messages from this thread
> > through linux-samsung-soc mailing list...
> > 
> > I believe linux-samsung-soc list exists to collect all threads related
> > to Samsung SoCs for people that don't want to subscribe to lists like
> > dri- devel, on which there is a lot of threads irrelevant to them,
> > with the risk of missing the important ones.
> > 
> > Please always make sure that any discussion about Samsung SoCs
> > (patches in particular) is going through linux-samsung-soc as well.
> 
> Thanks for your advice. As you said, some people might not want to
> subscribe to some mainling lists they don't want. And I think that the
> main mailing list on this patch is dri-devel so you must receive this
> email thread if you subscribed to the dri-devel.

I agree that dri-devel is the target mailing list for DRM patches, but 
AFAIK all threads related to Samsung SoCs should be sent to linux-samsung-
soc as well.

For example, I don't subscribe dri-devel, but I do linux-samsung-soc, 
because all I want to follow is all the works related to Samsung SoCs.
Remaining threads on dri-devel are outside of my competencies.

> Anyway it would be
> best to share this all mailing lists included in this email thread but
> if so, I have no doubt to receive email bumb. :(

Hmm, you don't have to subscribe to a mailing list to post to it.

Actually I'm wondering if the fact that your previous messages did not get 
to the linux-samsung-soc list was not caused by presence of HTML part in 
your messages, which is strongly discouraged on all mailing lists and 
actually blocked on vger.kernel.org where linux-samsung-soc is hosted.

Best regards,
Tomasz