From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] drm/i915: device params part 1
Date: Mon, 18 May 2020 19:47:47 +0300 [thread overview]
Message-ID: <20200518164750.11113-1-jani.nikula@intel.com> (raw)
This is the first 3 patches of [1], because apparently patch 4 breaks
the world. I've yet to pinpoint the issue, but these could move forward
in the meanwhile.
BR,
Jani.
[1] https://patchwork.freedesktop.org/series/77272/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2020-05-18 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 16:47 Jani Nikula [this message]
2020-05-18 16:47 ` [Intel-gfx] [PATCH 1/3] drm/i915/params: don't expose inject_probe_failure in debugfs Jani Nikula
2020-05-18 16:47 ` [Intel-gfx] [PATCH 2/3] drm/i915/params: fix i915.fake_lmem_start module param sysfs permissions Jani Nikula
2020-05-18 16:47 ` [Intel-gfx] [PATCH 3/3] drm/i915/params: prevent changing module params runtime Jani Nikula
2020-05-18 19:41 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/params: don't expose inject_probe_failure in debugfs Patchwork
2020-05-18 19:42 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-05-18 20:08 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2020-05-19 6:34 ` [Intel-gfx] drm/i915: device params part 1 Chris Wilson
2020-05-20 12:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] drm/i915/params: don't expose inject_probe_failure in debugfs (rev2) Patchwork
2020-05-20 12:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-05-20 13:06 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-05-21 3:52 ` [Intel-gfx] ✓ 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=20200518164750.11113-1-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;
as well as URLs for NNTP newsgroup(s).