From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Intel graphics driver community testing & development
<intel-gfx@lists.freedesktop.org>
Cc: Jani Nikula <jani.nikula@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2 2/2] drm/i915: Simplify i915_reg_read_ioctl
Date: Mon, 11 Sep 2017 10:59:13 +0300 [thread overview]
Message-ID: <1505116753.4107.2.camel@linux.intel.com> (raw)
In-Reply-To: <150488018215.21199.3153939108896876421@mail.alporthouse.com>
On Fri, 2017-09-08 at 15:16 +0100, Chris Wilson wrote:
> Quoting Joonas Lahtinen (2017-09-08 12:49:06)
> > Convert to use the freshly available made INTEL_GEN_MASK for easier
> > grepping and improve function readability and clarify the UABI
> > documentation.
> >
> > No functional changes.
> >
> > v2:
> > - Lift GEM_BUG_ONs and use is_power_of_2 (Chris)
> > - Retain -EINVAL on bad flags behavior (Chris)
>
> I think you missed git add.
Oh well, should not try to submit patches on Friday (or Monday for that
matter). Just did the git add and sent with -3 instead of -v3... But
the correct version is en route, too.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-11 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 11:49 [PATCH v2 1/2] drm/i915: Introduce INTEL_GEN_MASK Joonas Lahtinen
2017-09-08 11:49 ` [PATCH v2 2/2] drm/i915: Simplify i915_reg_read_ioctl Joonas Lahtinen
2017-09-08 14:16 ` Chris Wilson
2017-09-11 7:59 ` Joonas Lahtinen [this message]
2017-09-08 12:07 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/2] drm/i915: Introduce INTEL_GEN_MASK Patchwork
2017-09-08 14:51 ` ✓ Fi.CI.IGT: " 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=1505116753.4107.2.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@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