From: Daniel Vetter <daniel@ffwll.ch>
To: Deepak S <deepak.s@linux.intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] drm/i915/chv: Populate total EU count on Cherryview
Date: Tue, 20 Jan 2015 10:06:05 +0100 [thread overview]
Message-ID: <20150120090605.GE10113@phenom.ffwll.local> (raw)
In-Reply-To: <54BDC669.2020004@linux.intel.com>
On Tue, Jan 20, 2015 at 08:37:21AM +0530, Deepak S wrote:
>
> On Monday 19 January 2015 03:14 PM, Daniel Vetter wrote:
> >On Fri, Jan 16, 2015 at 08:42:16PM +0530, deepak.s@linux.intel.com wrote:
> >>From: Deepak S <deepak.s@linux.intel.com>
> >>
> >>Starting with Cherryview, devices may have a varying number of EU for
> >>a given ID due to creative fusing. Punit support different frequency for
> >>different fuse data. We use this patch to help get total eu enabled and
> >>read the right offset to get RP0
> >>
> >>Based upon a patch from Jeff, but reworked to only store eu_total and
> >>avoid sending info to userspace
> >>
> >>v2: Format register definitions (Jani)
> >>
> >>Signed-off-by: Deepak S <deepak.s@linux.intel.com>
> >>Signed-off-by: Jeff McGee <jeff.mcgee@intel.com>
> >This isn't really how sob works. The last line _must_ be the person who
> >last touched the patch, otherwise you're doing it wrong. Since this patch
> >doesn't seem to be from Jeff I've dropped his sobline and converted to an
> >ack.
> >
> >Really if you just want to acknowledge people who have contributed to a
> >patch (e.g. you've based your patch on some version of theirs) do that in
> >the commit message + Cc:
> >-Daniel
>
> Oh Sorry. I was not aware of this. I will follow the guidelines in future patch submission.
Yeah I think most examples of sob abuse come from vpg display, so updating
your guidelines would be good.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-20 9:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 8:48 [PATCH 1/4] drm/i915/chv: Use timeout mode for RC6 on chv deepak.s
2014-12-12 8:48 ` [PATCH 2/4] drm/i915/chv: Populate total EU count on Cherryview deepak.s
2014-12-11 12:09 ` Jani Nikula
2014-12-12 12:10 ` Deepak S
2014-12-12 12:33 ` [PATCH v2] " deepak.s
2014-12-12 8:48 ` [PATCH 3/4] drm/i915: New offset for reading frequencies on CHV deepak.s
2014-12-12 19:09 ` Ville Syrjälä
2014-12-15 6:51 ` Jani Nikula
2014-12-16 12:11 ` Deepak S
2015-01-16 15:12 ` [PATCH v2 0/3] Use new turbo offset for chv production system deepak.s
2015-01-16 15:12 ` [PATCH v2 1/3] drm/i915/chv: Populate total EU count on Cherryview deepak.s
2015-01-16 16:06 ` Jeff McGee
2015-01-16 17:11 ` Ville Syrjälä
2015-01-19 9:44 ` Daniel Vetter
2015-01-20 3:07 ` Deepak S
2015-01-20 9:06 ` Daniel Vetter [this message]
2015-01-16 15:12 ` [PATCH v2 2/3] drm/i915: Increase the range of sideband address deepak.s
2015-01-16 17:11 ` Ville Syrjälä
2015-01-16 15:12 ` [PATCH v2 3/3] drm/i915: New offset for reading frequencies on CHV deepak.s
2015-01-16 17:09 ` Ville Syrjälä
2015-01-17 5:34 ` Deepak S
2015-01-17 5:35 ` [PATCH v3] " deepak.s
2015-01-19 9:47 ` Daniel Vetter
2014-12-12 8:48 ` [PATCH 4/4] drm/i915: Skip gunit save/restore for cherryview deepak.s
2014-12-11 12:02 ` Ville Syrjälä
2014-12-15 15:16 ` Daniel Vetter
2014-12-13 6:13 ` [PATCH v2] drm/i915/chv: Use timeout mode for RC6 on chv deepak.s
2014-12-12 16:34 ` Ville Syrjälä
2014-12-16 12:09 ` Deepak S
2014-12-15 15:12 ` Daniel Vetter
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=20150120090605.GE10113@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=deepak.s@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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