From: Jani Nikula <jani.nikula@linux.intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dmc: Use RUNTIME_INFO->stp for DMC
Date: Mon, 05 Jul 2021 10:45:11 +0300 [thread overview]
Message-ID: <87r1gd9pbs.fsf@intel.com> (raw)
In-Reply-To: <20210704053202.dncjlbkingckz4gg@ldmartin-desk2>
On Sat, 03 Jul 2021, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> On Fri, Jul 02, 2021 at 10:49:05AM +0300, Jani Nikula wrote:
>>Frankly, I think all of this should be incorporated to intel_step.[ch]
>>instead of having a semi-overlapping handling here. Just look at the
>>amount of duplication already.
>
> I guess you missed I gave the same suggestion below and that there is
> already a new version of this patch? Question here was about going a
> step further to avoid the conversion STEP_* to 2 chars.
Sorry for the noise.
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:[~2021-07-05 7:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 23:06 [Intel-gfx] [PATCH] drm/i915/dmc: Use RUNTIME_INFO->stp for DMC Anusha Srivatsa
2021-06-30 23:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-06-30 23:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-06-30 23:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-01 0:01 ` [Intel-gfx] [PATCH] " Lucas De Marchi
2021-07-01 0:15 ` Souza, Jose
2021-07-01 0:17 ` Lucas De Marchi
2021-07-01 17:46 ` Lucas De Marchi
2021-07-02 7:49 ` Jani Nikula
2021-07-04 5:34 ` Lucas De Marchi
2021-07-05 7:45 ` Jani Nikula [this message]
2021-07-01 5:48 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
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=87r1gd9pbs.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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