Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 0/2] drm/i915: split out i915_driver.[ch]
Date: Fri, 22 Oct 2021 18:52:31 +0300	[thread overview]
Message-ID: <cover.1634917858.git.jani.nikula@intel.com> (raw)

i915_drv.h is mostly not about i915_drv.c, so make the distinction clear
by renaming i915_drv.c to i915_driver.c and splitting out i915_driver.h
from i915_drv.h.

Jani Nikula (2):
  drm/i915/driver: rename i915_drv.c to i915_driver.c
  drm/i915/driver: rename driver to i915_drm_driver

 drivers/gpu/drm/i915/Makefile                 |  2 +-
 .../drm/i915/{i915_drv.c => i915_driver.c}    | 11 +++++----
 drivers/gpu/drm/i915/i915_driver.h            | 24 +++++++++++++++++++
 drivers/gpu/drm/i915/i915_drv.h               | 11 +--------
 drivers/gpu/drm/i915/i915_pci.c               |  1 +
 drivers/gpu/drm/i915/i915_switcheroo.c        |  1 +
 6 files changed, 34 insertions(+), 16 deletions(-)
 rename drivers/gpu/drm/i915/{i915_drv.c => i915_driver.c} (99%)
 create mode 100644 drivers/gpu/drm/i915/i915_driver.h

-- 
2.30.2


             reply	other threads:[~2021-10-22 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 15:52 Jani Nikula [this message]
2021-10-22 15:52 ` [Intel-gfx] [PATCH 1/2] drm/i915/driver: rename i915_drv.c to i915_driver.c Jani Nikula
2021-10-22 15:52 ` [Intel-gfx] [PATCH 2/2] drm/i915/driver: rename driver to i915_drm_driver Jani Nikula
2021-10-22 20:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: split out i915_driver.[ch] Patchwork
2021-10-22 20:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-10-22 20:36 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-23  3:51 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=cover.1634917858.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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