From: "Hwang, Dongseong" <dongseong.hwang@intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: "Stéphane Marchesin" <marcheu@chromium.org>,
"Daniele Castagna" <dcastagna@chromium.org>,
"ML dri-devel" <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2] libdrm/fourcc: Add formats R8, RG88, GR88, NV24, NV42
Date: Fri, 22 Apr 2016 12:03:51 +0300 [thread overview]
Message-ID: <CAFVCBbEfm95nPv5m3Re81HT40w6jZpnr+9tLJfvWYRMfb6LE9A@mail.gmail.com> (raw)
In-Reply-To: <CACvgo53thy9of84cbSj-0LtS49LL_1+Ow5SDBJSt=7kEf_=qXQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1296 bytes --]
I incorrectly interpreted your comments. I thought you want me to reply
every feedback.
It's first trial for me to contribute on linux. sorry for lots of noise.
I've learnt linux practice. next time it will be more smooth.
My undesirable behavior doesn't represent CrOS development. CrOS
development keeps in mind of product, so also prefers quality and
robustness.
I checked the change is already landed. Close this patch as WontFix.
Thanks you for good guidance.
Dongseong
On Thu, Apr 21, 2016 at 8:56 PM, Emil Velikov <emil.l.velikov@gmail.com>
wrote:
> On 21 April 2016 at 18:46, Dongseong Hwang <dongseong.hwang@intel.com>
> wrote:
> > Produced from headers_install of 9dabb0053b63bc32ab6ad5d13209d1e43395313f
> > (drm-intel-nightly) in the kernel.
> >
> > ChromeOS will use new format to optimize video decoding.
> >
> Did you check before sending the patch out ?
> As mentioned over IRC a few times - there's no need for the
> update.danvet already sorted it out.
>
> Also, I realise that CrOS development is quite high paced, although
> some of us prefer quality over quantity. Meaning: don't send multiple
> emails (spam?) if you have not covered (ideally) all the concerns
> mentioned. Not doing so is one of the ways to alienate developers.
>
> Pretty please ?
>
> Thanks
> Emil
>
[-- Attachment #1.2: Type: text/html, Size: 1896 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-04-22 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 17:46 [PATCH v2] libdrm/fourcc: Add formats R8, RG88, GR88, NV24, NV42 Dongseong Hwang
2016-04-21 17:56 ` Emil Velikov
2016-04-22 9:03 ` Hwang, Dongseong [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=CAFVCBbEfm95nPv5m3Re81HT40w6jZpnr+9tLJfvWYRMfb6LE9A@mail.gmail.com \
--to=dongseong.hwang@intel.com \
--cc=dcastagna@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.l.velikov@gmail.com \
--cc=marcheu@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).