From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC 1/2] drm/i915: move modesetting output/encoder code under display/
Date: Tue, 11 Jun 2019 10:24:07 -0700 [thread overview]
Message-ID: <20190611172407.GI22504@intel.com> (raw)
In-Reply-To: <156023922792.8761.12591683023011404476@skylake-alporthouse-com>
On Tue, Jun 11, 2019 at 08:47:07AM +0100, Chris Wilson wrote:
> Quoting Jani Nikula (2019-06-10 22:53:11)
> > Add a new subdirectory for display code, and start off by moving
> > modesetting output/encoder code. Judging by the include changes, this is
> > a surprisingly clean operation.
> >
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Only surprisingly clean because you already done the hard work :)
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-11 17:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 21:53 [RFC 1/2] drm/i915: move modesetting output/encoder code under display/ Jani Nikula
2019-06-10 21:53 ` [RFC 2/2] drm/i915: move modesetting core " Jani Nikula
2019-06-11 7:52 ` Chris Wilson
2019-06-11 17:24 ` Rodrigo Vivi
2019-06-10 22:46 ` ✓ Fi.CI.BAT: success for series starting with [RFC,1/2] drm/i915: move modesetting output/encoder " Patchwork
2019-06-11 7:47 ` [RFC 1/2] " Chris Wilson
2019-06-11 17:24 ` Rodrigo Vivi [this message]
2019-06-12 5:38 ` ✓ Fi.CI.IGT: success for series starting with [RFC,1/2] " 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=20190611172407.GI22504@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.