From: Jani Nikula <jani.nikula@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 1/2] drm/i915: move intel_csr.[ch] under display/
Date: Tue, 11 Feb 2020 18:32:42 +0200 [thread overview]
Message-ID: <877e0tythx.fsf@intel.com> (raw)
In-Reply-To: <20200211162903.GW13686@intel.com>
On Tue, 11 Feb 2020, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> On Tue, Feb 11, 2020 at 06:14:50PM +0200, Jani Nikula wrote:
>> The DMC firmware is about display. Move the handling under display. No
>> functional changes.
>>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Acked-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> I'm also thinking s/csr/dmc/ migth be a good idea. I don't even
> remember what "csr" means...
Context Save & Restore, perhaps? I'll save the rename for another day,
and another patch.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-11 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 16:14 [Intel-gfx] [PATCH v2 1/2] drm/i915: move intel_csr.[ch] under display/ Jani Nikula
2020-02-11 16:14 ` [Intel-gfx] [PATCH v2 2/2] drm/i915: split out display debugfs to a separate file Jani Nikula
2020-02-14 11:07 ` Chris Wilson
2020-02-14 11:44 ` Jani Nikula
2020-02-11 16:29 ` [Intel-gfx] [PATCH v2 1/2] drm/i915: move intel_csr.[ch] under display/ Ville Syrjälä
2020-02-11 16:32 ` Chris Wilson
2020-02-14 7:06 ` Jani Nikula
2020-02-11 16:32 ` Jani Nikula [this message]
2020-02-13 20:03 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v2,1/2] " Patchwork
2020-03-02 15:53 ` [Intel-gfx] [PATCH v2 1/2] " Ville Syrjälä
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=877e0tythx.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).