From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dave Gordon <david.s.gordon@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] Prefer INTEL_INFO(dev_priv) to INTEL_INFO(dev)
Date: Mon, 11 Apr 2016 12:53:52 +0300 [thread overview]
Message-ID: <87twj8tqrz.fsf@intel.com> (raw)
In-Reply-To: <570B6DC5.7050609@intel.com>
On Mon, 11 Apr 2016, Dave Gordon <david.s.gordon@intel.com> wrote:
> For this reason, I'd like to recommend that anyone doing this sort of
> bulk transformation with Cocci or awk or just sed should /always/
> include the transformation script to help those with patches in flight.
I think that's generally the expectation anyway for cocci changes.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-11 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 8:08 [PATCH v4 1/3] drm/i915: Use i915_vm_to_ppgtt instead of manual container_of Joonas Lahtinen
2016-04-07 8:08 ` [PATCH v4 2/3] drm/i915: Do not WARN_ON in i915_vm_to_ppgtt Joonas Lahtinen
2016-04-07 8:08 ` [PATCH v4 3/3] drm/i915: Do not use {HAS_*, IS_*, INTEL_INFO}(dev_priv->dev) Joonas Lahtinen
2016-04-07 17:57 ` [RFC] Prefer INTEL_INFO(dev_priv) to INTEL_INFO(dev) Dave Gordon
2016-04-08 6:09 ` Joonas Lahtinen
2016-04-11 9:26 ` Dave Gordon
2016-04-11 9:53 ` Jani Nikula [this message]
2016-04-07 11:31 ` ✗ Fi.CI.BAT: failure for series starting with [v4,1/3] drm/i915: Use i915_vm_to_ppgtt instead of manual container_of Patchwork
2016-04-07 11:53 ` Joonas Lahtinen
2016-04-08 8:58 ` ✗ Fi.CI.BAT: failure for series starting with [v4,1/3] drm/i915: Use i915_vm_to_ppgtt instead of manual container_of (rev2) 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=87twj8tqrz.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=david.s.gordon@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@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 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.