From: Inki Dae <inki.dae@samsung.com>
To: Tobias Jakobi <liquid.acid@gmx.net>
Cc: Javier Martinez Canillas <javier@dowhile0.org>,
Daniel Stone <daniels@collabora.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH] drm: Exynos: Respect framebuffer pitch for FIMD/Mixer
Date: Fri, 27 Mar 2015 10:47:55 +0900 [thread overview]
Message-ID: <5514B6CB.7060301@samsung.com> (raw)
In-Reply-To: <5514A118.2000609@gmx.net>
On 2015년 03월 27일 09:15, Tobias Jakobi wrote:
> Inki Dae wrote:
>> Hello Javier,
>>
>> Applied.
>>
>> Could you use right prefix of the subject like below when you post patch?
>>
>> 'drm/exynos: ...', not 'drm: Exynos: ...'
>>
>> Your email will be filtered from my mailbox if you don't use the right
>> prefix so I couldn't check and take care of your patch.
> I would suggest to change (or drop) the filter settings then. I don't
Filters of my mailbox are considered for two cases, one is DRI mailing
list, other is drm/exynos.
So if you don't use the drm/exynos prefix, then I would try to find your
patch in DRI mailing list - I sometimes check the mailing list. However,
the mailing list have so much emails so it'd be not easy to pick up only
exynos relevant patches among the email lists. As a result, you would
get the my review lately.
> think you can expect people to jump through these hoops to reach a
> maintainer of a kernel subsystem. Especially since this not 'documented'
> anywhere.
Right, this is not documented but if you have ever checked exynos drm
driver tree, then I think you could know how we use the prefix. Of
course, I don't like to force the use of this prefix but if you and
other people use prefix in the manner of them, exynos drm tree would be
a little bit messy. i.e., DRM: EXYNOS, drm: exynos, drm: Exynos,
drm/exynos, drm/exynos: fimd, drm: exynos: fimd, DRM: EXYNOS: FIMD, ...
so many cases.... Do you really want this?
So I will always say "please, use right prefix" Otherwise, I will change
it while merging as is.
And I see that other drm drivers have their own way which is not
documented but just implicitly.
Thanks,
Inki Dae
>
>
>
> With best wishes,
> Tobias
>
>
next prev parent reply other threads:[~2015-03-27 1:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 13:24 [PATCH] drm: Exynos: Respect framebuffer pitch for FIMD/Mixer Daniel Stone
2015-03-24 8:57 ` Javier Martinez Canillas
2015-03-26 14:32 ` Inki Dae
2015-03-26 14:48 ` Daniel Stone
2015-03-27 1:55 ` Inki Dae
2015-03-27 0:15 ` Tobias Jakobi
2015-03-27 1:47 ` Inki Dae [this message]
2015-03-27 11:08 ` Javier Martinez Canillas
2015-03-27 16:28 ` 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=5514B6CB.7060301@samsung.com \
--to=inki.dae@samsung.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javier@dowhile0.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=liquid.acid@gmx.net \
--cc=m.szyprowski@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox