From: Jani Nikula <jani.nikula@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH] gpu/drm/i915: globally replace dev_priv with i915
Date: Thu, 13 Jun 2019 16:12:37 +0300 [thread overview]
Message-ID: <87pnnhwrwa.fsf@intel.com> (raw)
In-Reply-To: <20190612162900.13777-1-lucas.demarchi@intel.com>
On Wed, 12 Jun 2019, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> We are slowly converting dev_priv to i915 everywhere, spread into
> smaller series. While this is good to avoid unrelated breakages to other
> inflight patches, it's bad because inflight patches on nearby paths keep
> breaking. Paired with other code moves and refactores this is becoming a
> nightmare.
>
> Now that I915_{READ,WRITE} are gone and implicit access to dev_priv no
> longer exists we can simply sed all files and be done with the
> conversion. This was generated with the following commands with no
> additional fixups:
>
> git ls-files --full-name -z -- drivers/gpu/drm/i915/ | \
> xargs -0 sed -i 's/\bdev_priv\b/i915/g'
>
> Any pending series can apply the same search and replace when rebasing.
I'm pretty strongly against renaming the implicit dev_priv local
variable before we've gotten rid of it. Renaming s/dev_priv/i915/ upon
converting a function to not use the implicit dev_priv helps us by
catching any leftover references.
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:[~2019-06-13 13:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190612162900.13777-1-lucas.demarchi@intel.com>
2019-06-13 1:02 ` ✗ Fi.CI.CHECKPATCH: warning for gpu/drm/i915: globally replace dev_priv with i915 Patchwork
2019-06-13 1:03 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-06-13 2:19 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-13 6:07 ` [PATCH] " Chris Wilson
2019-06-13 6:14 ` Lucas De Marchi
2019-06-13 13:12 ` Jani Nikula [this message]
2019-06-13 16:29 ` Lucas De Marchi
2019-06-13 16:48 ` Lucas De Marchi
2019-06-13 17:04 ` Rodrigo Vivi
2019-06-14 12:47 ` Jani Nikula
2019-06-14 17:06 ` Lucas De Marchi
[not found] ` <0000a4b2-ac8b-a18d-4c78-0db197c712a1@linux.intel.com>
2019-06-13 15:19 ` Chris Wilson
2019-06-13 15:21 ` Tvrtko Ursulin
2019-06-14 16:41 ` ✓ Fi.CI.IGT: success 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=87pnnhwrwa.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 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.