From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [PATCH 0/1] Start cleaning up register definitions
Date: Fri, 07 Jan 2022 11:53:10 +0200 [thread overview]
Message-ID: <87a6g7na7t.fsf@intel.com> (raw)
In-Reply-To: <87czl3nb27.fsf@intel.com>
On Fri, 07 Jan 2022, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> Another early step should be splitting out the non-MMIO macros, for
> example the IOSF and PUNIT sideband stuff. They don't necessarily fall
> to the below categories.
Funny. I actually had a branch from a few months back splitting out PCI
config space, VGA, and VLV sideband registers. Added some commit
messages and sent it out. [1]
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/98597/
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-01-07 9:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 23:08 [Intel-gfx] [PATCH 0/1] Start cleaning up register definitions Matt Roper
2022-01-06 23:08 ` [Intel-gfx] [PATCH 1/1] drm/i915: Drop unused " Matt Roper
2022-01-07 10:46 ` Jani Nikula
2022-01-07 16:46 ` Lucas De Marchi
2022-01-10 10:55 ` Jani Nikula
2022-01-10 16:11 ` Lucas De Marchi
2022-01-06 23:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Start cleaning up " Patchwork
2022-01-06 23:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-07 0:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-07 9:34 ` [Intel-gfx] [PATCH 0/1] " Jani Nikula
2022-01-07 9:53 ` Jani Nikula [this message]
2022-01-07 16:14 ` [Intel-gfx] ✓ 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=87a6g7na7t.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@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