All of lore.kernel.org
 help / color / mirror / Atom feed
From: Inki Dae <daeinki@gmail.com>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org,
	Sachin Kamat <sachin.kamat@linaro.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	sunil joshi <joshi@samsung.com>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	"kgene.kim" <kgene.kim@samsung.com>,
	Vikas Sajjan <vikas.sajjan@linaro.org>
Subject: Re: [PATCH v4] drm/exynos: prepare FIMD clocks
Date: Sun, 21 Apr 2013 23:05:45 +0900	[thread overview]
Message-ID: <CAAQKjZN78+WTO+Q3eWDAS2iF3zPxo7tjysAd3nwbGEKXmz8zUQ@mail.gmail.com> (raw)
In-Reply-To: <2021753.aZ0KODlsRB@flatron>


[-- Attachment #1.1: Type: text/plain, Size: 1615 bytes --]

2013/4/21 Tomasz Figa <tomasz.figa@gmail.com>

> On Sunday 21 of April 2013 13:23:10 Viresh Kumar wrote:
> > On 20 April 2013 20:56, Inki Dae <inki.dae@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. 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. :(

Thanks,
Inki Dae


> Thanks in advance.
>
> Best regards,
> Tomasz
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>

[-- Attachment #1.2: Type: text/html, Size: 2609 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2013-04-21 14:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08 11:07 [PATCH v4] drm/exynos: prepare FIMD clocks Vikas Sajjan
2013-04-08 11:11 ` Viresh Kumar
2013-04-19  8:55   ` Vikas Sajjan
2013-04-20 15:26     ` Inki Dae
2013-04-21  7:24       ` Vikas Sajjan
2013-04-21  7:53       ` Viresh Kumar
2013-04-21 10:35         ` Tomasz Figa
2013-04-21 14:05           ` Inki Dae [this message]
2013-04-21 14:15             ` Tomasz Figa
2013-04-21 10:26   ` Tomasz Figa
2013-04-21 13:36     ` Inki Dae
2013-04-21 14:43       ` Tomasz Figa
2013-04-22  5:11         ` Inki Dae
2013-04-22  9:52           ` Tomasz Figa
2013-04-22 10:03             ` Inki Dae
2013-04-22 10:17               ` Sylwester Nawrocki
2013-04-22 10:20                 ` Inki Dae
2013-04-22 10:37                 ` Tomasz Figa
2013-04-22 11:42                   ` Rafael J. Wysocki
2013-04-22 12:04                     ` Inki Dae
2013-04-23 11:51                       ` myungjoo.ham
2013-04-23 12:09                         ` Inki Dae
2013-04-22 11:52                   ` Inki Dae
2013-04-22  5:14         ` Viresh Kumar
2013-04-22  9:56           ` Tomasz Figa
2013-04-22 10:05             ` Sylwester Nawrocki
2013-04-22 12:30               ` Tomasz Figa
2013-04-22 10:26             ` Viresh Kumar

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=CAAQKjZN78+WTO+Q3eWDAS2iF3zPxo7tjysAd3nwbGEKXmz8zUQ@mail.gmail.com \
    --to=daeinki@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=joshi@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=sachin.kamat@linaro.org \
    --cc=tomasz.figa@gmail.com \
    --cc=vikas.sajjan@linaro.org \
    --cc=viresh.kumar@linaro.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.