intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915/params: fix i915.reset module param type
Date: Tue, 02 Jun 2020 16:16:43 +0100	[thread overview]
Message-ID: <159111100381.29407.10499392760570265777@build.alporthouse.com> (raw)
In-Reply-To: <20200602151126.25626-1-jani.nikula@intel.com>

Quoting Jani Nikula (2020-06-02 16:11:26)
> The reset member in i915_params was previously changed to unsigned, but
> this failed to change the actual module parameter.
> 
> Fixes: aae970d8454b ("drm/i915: Mark i915.reset as unsigned")
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-06-02 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 15:11 [Intel-gfx] [PATCH] drm/i915/params: fix i915.reset module param type Jani Nikula
2020-06-02 15:16 ` Chris Wilson [this message]
2020-06-04  9:31   ` Jani Nikula
2020-06-02 15:34 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-06-02 15:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-06-02 23:05 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-06-03 15:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/params: fix i915.reset module param type (rev2) Patchwork
2020-06-03 15:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-06-04  4:50 ` [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=159111100381.29407.10499392760570265777@build.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).