From: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] drm/i915: fix spelling mistake "reserverd" -> "reserved"
Date: Wed, 21 Nov 2018 13:14:33 +0200 [thread overview]
Message-ID: <87pnuyel7q.fsf@intel.com> (raw)
In-Reply-To: <20181120151415.32419-1-alexandre.belloni@bootlin.com>
On Tue, 20 Nov 2018, Alexandre Belloni <alexandre.belloni@bootlin.com> wrote:
> Fix a spelling mistake in a comment.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Thanks for the patch, pushed to drm-intel-next-queued.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index f9ce35da4123..742f8ff101e4 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -4280,7 +4280,7 @@ static void gen10_sseu_device_status(struct drm_i915_private *dev_priv,
> for (s = 0; s < info->sseu.max_slices; s++) {
> /*
> * FIXME: Valid SS Mask respects the spec and read
> - * only valid bits for those registers, excluding reserverd
> + * only valid bits for those registers, excluding reserved
> * although this seems wrong because it would leave many
> * subslices without ACK.
> */
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2018-11-21 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 15:14 [PATCH] drm/i915: fix spelling mistake "reserverd" -> "reserved" Alexandre Belloni
2018-11-21 1:43 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-11-21 11:14 ` Jani Nikula [this message]
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=87pnuyel7q.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@bootlin.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@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).