public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: deepak.s@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, benjamin.widawsky@intel.com
Subject: Re: [PATCH v2] drm/i915: Match debugfs interface name to new RPS naming
Date: Mon, 31 Mar 2014 10:43:20 +0200	[thread overview]
Message-ID: <20140331084320.GR22327@phenom.ffwll.local> (raw)
In-Reply-To: <1396245602-2341-1-git-send-email-deepak.s@linux.intel.com>

On Mon, Mar 31, 2014 at 11:30:02AM +0530, deepak.s@linux.intel.com wrote:
> From: Deepak S <deepak.s@linux.intel.com>
> 
> Let's change the i915_cur_delayinfo to i915_frequency_info to be in sync
> with new RPS naming convention.
> 
> v2: Add "i915_frequency_info" as debugfs interface name (Ben)
> 
> Signed-off-by: Deepak S <deepak.s@linux.intel.com>

Yeah, I always need to do a grep .* CAGF to find this file ;-) Queued for
-next, thanks for the patch.
-Daniel

> ---
>  drivers/gpu/drm/i915/i915_debugfs.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 1a35215..e5d9a902 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -966,7 +966,7 @@ static int i915_rstdby_delays(struct seq_file *m, void *unused)
>  	return 0;
>  }
>  
> -static int i915_cur_delayinfo(struct seq_file *m, void *unused)
> +static int i915_frequency_info(struct seq_file *m, void *unused)
>  {
>  	struct drm_info_node *node = (struct drm_info_node *) m->private;
>  	struct drm_device *dev = node->minor->dev;
> @@ -3786,7 +3786,7 @@ static const struct drm_info_list i915_debugfs_list[] = {
>  	{"i915_gem_hws_bsd", i915_hws_info, 0, (void *)VCS},
>  	{"i915_gem_hws_vebox", i915_hws_info, 0, (void *)VECS},
>  	{"i915_rstdby_delays", i915_rstdby_delays, 0},
> -	{"i915_cur_delayinfo", i915_cur_delayinfo, 0},
> +	{"i915_frequency_info", i915_frequency_info, 0},
>  	{"i915_delayfreq_table", i915_delayfreq_table, 0},
>  	{"i915_inttoext_table", i915_inttoext_table, 0},
>  	{"i915_drpc_info", i915_drpc_info, 0},
> -- 
> 1.9.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-03-31  8:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-30  8:21 [PATCH] drm/i915: Match debugfs interface name to new RPS naming deepak.s
2014-03-30 19:19 ` Ben Widawsky
2014-03-31  6:00 ` [PATCH v2] " deepak.s
2014-03-31  8:43   ` Daniel Vetter [this message]
2014-03-31 18:08   ` Ben Widawsky

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=20140331084320.GR22327@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=benjamin.widawsky@intel.com \
    --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