From: Paul Menzel <paulepanter@users.sourceforge.net>
To: InKi Dae <inki.dae@samsung.com>
Cc: "Mandeep Singh Baines" <msb@chromium.org>,
"Stéphane Marchesin" <marcheu@chromium.org>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/exynos: fix double call of drm_prime_(init/destroy)_file_private
Date: Thu, 06 Sep 2012 09:50:33 +0200 [thread overview]
Message-ID: <1346917833.10162.4.camel@mattotaupa> (raw)
In-Reply-To: <CAAQKjZPGefy9333AGTN1iwxWuCiPvi85raDE7ijDmRcm9PPWWw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
Dear Inki Dae,
Am Donnerstag, den 06.09.2012, 11:35 +0900 schrieb InKi Dae:
> 2012/9/6 Mandeep Singh Baines <msb@chromium.org>:
> > The double invocations are incorrect but seem to be safe so I don't
> > think this will fix any bugs.
> >
> > Before:
> >
> > [ 7.639366] drm_prime_init_file ee3675d0
> > [ 7.639377] drm_prime_init_file ee3675d0
> > [ 7.639507] drm_prime_destroy_file ee3675d0
> > [ 7.639518] drm_prime_destroy_file ee3675d0
> > [ 7.639802] drm_prime_init_file ee372390
> > [ 7.639810] drm_prime_init_file ee372390
> > [ 8.473316] drm_prime_init_file ee356390
> > [ 8.473331] drm_prime_init_file ee356390
> >
> > After:
> >
> > [ 6.363842] drm_prime_init_file edc2e5d0
> > [ 6.363994] drm_prime_destroy_file edc2e5d0
> > [ 6.364260] drm_prime_init_file edc2e750
> > [ 8.004837] drm_prime_init_file ee36ded0
> >
> > Signed-off-by: Mandeep Singh Baines <msb@chromium.org>
> > CC: Stéphane Marchesin <marcheu@chromium.org>
> > CC: Pawel Osciak <posciak@google.com>
> > CC: Inki Dae <inki.dae@samsung.com>
> > CC: Joonyoung Shim <jy0922.shim@samsung.com>
> > CC: Seung-Woo Kim <sw0312.kim@samsung.com>
> > CC: Kyungmin Park <kyungmin.park@samsung.com>
> > CC: David Airlie <airlied@linux.ie>
> > CC: dri-devel@lists.freedesktop.org
>
> remove all CCs
I guess they were generated by some script. So they should be fine, no?
Mandeep, if you put CC in here those people should be CCed in real. `git
send-email` should take care of that but I do not see everyone in the CC
field. Or does `git send-email` use blind carbon copy (BCC) field?
> and can you send it again using text mode?
At least to the list it was send in plain text mode.
> your patch is messed up when I try to get patch file.
Everything is fine on my side. Especially since Mandeep used `git
send-email` which should do everything correctly.
> Thanks.
> Inki Dae
In your From address your name is written InKi with capital K. Which one
is correct?
Thanks,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-09-06 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 21:47 Mandeep Singh Baines
2012-09-06 2:15 ` 김승우
2012-09-06 2:35 ` InKi Dae
2012-09-06 7:50 ` Paul Menzel [this message]
2012-09-06 8:30 ` InKi Dae
2012-09-06 16:49 ` Mandeep Singh Baines
2012-09-07 4:49 ` 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=1346917833.10162.4.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=msb@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
all inboxes | Powered by JetHome®