From: Mika Kahola <mika.kahola@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/5] drm/i915: Miscellaneous fixes to reduce dependency for I915_MAX_PIPES
Date: Tue, 10 Oct 2017 12:24:33 +0300 [thread overview]
Message-ID: <1507627473.3274.94.camel@intel.com> (raw)
In-Reply-To: <20171010091916.GN10981@intel.com>
On Tue, 2017-10-10 at 12:19 +0300, Ville Syrjälä wrote:
> On Thu, Sep 14, 2017 at 10:53:01AM +0300, Mika Kahola wrote:
> >
> > This patch series introduces fixes to reduce dependency for
> > I915_MAX_PIPES and minor optimizations to reduce hardcoding.
> >
> > Kahola, Mika (1):
> > drm/i915: Remove I915_MAX_PIPES dependency for DDB allocation
> >
> > Mika Kahola (4):
> > drm/i915: Don't relay on I915_MAX_PIPES
> > drm/i915: Fold IRQ pipe masks
> > drm/i915: Favor for_each_pipe() macro
> > drm/i915: Cleanup South Error Interrupts
> I replied with a few minor nits to the individual patches. Ttoally up
> to
> you whether you want to do those changes or not.
>
> For the series
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Thanks Ville for review. I will change it 'enum pipe pipe'. It's
cleaner that way.
>
> >
> >
> > drivers/gpu/drm/i915/i915_irq.c | 19 +++++++------------
> > drivers/gpu/drm/i915/i915_reg.h | 3 ---
> > drivers/gpu/drm/i915/intel_audio.c | 2 +-
> > drivers/gpu/drm/i915/intel_display.c | 5 ++++-
> > drivers/gpu/drm/i915/intel_drv.h | 3 ++-
> > drivers/gpu/drm/i915/intel_pipe_crc.c | 9 +++++----
> > drivers/gpu/drm/i915/intel_pm.c | 6 ++++--
> > 7 files changed, 23 insertions(+), 24 deletions(-)
> >
> > --
> > 2.7.4
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Mika Kahola - Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-10 9:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 7:53 [PATCH 0/5] drm/i915: Miscellaneous fixes to reduce dependency for I915_MAX_PIPES Mika Kahola
2017-09-14 7:53 ` [PATCH 1/5] drm/i915: Don't relay on I915_MAX_PIPES Mika Kahola
2017-09-14 7:53 ` [PATCH 2/5] drm/i915: Remove I915_MAX_PIPES dependency for DDB allocation Mika Kahola
2017-10-10 9:15 ` Ville Syrjälä
2017-09-14 7:53 ` [PATCH 3/5] drm/i915: Fold IRQ pipe masks Mika Kahola
2017-09-14 7:53 ` [PATCH 4/5] drm/i915: Favor for_each_pipe() macro Mika Kahola
2017-10-10 9:17 ` Ville Syrjälä
2017-09-14 7:53 ` [PATCH 5/5] drm/i915: Cleanup South Error Interrupts Mika Kahola
2017-09-14 8:10 ` ✓ Fi.CI.BAT: success for drm/i915: Miscellaneous fixes to reduce dependency for I915_MAX_PIPES Patchwork
2017-09-14 9:12 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-09-15 17:58 ` Rodrigo Vivi
2017-09-18 12:06 ` Mika Kahola
2017-09-21 10:26 ` Mika Kahola
2017-09-18 15:12 ` ✗ Fi.CI.BAT: failure " Patchwork
2017-09-19 16:05 ` Patchwork
2017-09-27 11:02 ` ✓ Fi.CI.BAT: success " Patchwork
2017-10-05 8:29 ` Patchwork
2017-10-10 8:34 ` Patchwork
2017-10-10 9:19 ` [PATCH 0/5] " Ville Syrjälä
2017-10-10 9:24 ` Mika Kahola [this message]
2017-10-10 9:20 ` Kenneth Graunke
2017-10-10 9:59 ` Mika Kahola
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=1507627473.3274.94.camel@intel.com \
--to=mika.kahola@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