From: "Mun, Gwan-gyeong" <gwan-gyeong.mun@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"airlied@linux.ie" <airlied@linux.ie>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix typo in i915_drm_resume()
Date: Mon, 6 Aug 2018 06:13:05 +0000 [thread overview]
Message-ID: <251f85f6cca248b7db7289d53f984892d41c67e2.camel@intel.com> (raw)
In-Reply-To: <153332352090.15394.16477722089065680950@skylake-alporthouse-com>
On Fri, 2018-08-03 at 20:12 +0100, Chris Wilson wrote:
> Quoting Gwan-gyeong Mun (2018-08-03 17:41:50)
>
> Even for trivial patches, always include a changelog. In this case, I
> added "Trivial typo, s/loose/lose/, in i915_drm_resume."
>
> > Signed-off-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> And pushed, thanks for the spelling correction.
> -Chris
Hi Chris,
Thank you for guiding me and reviewing it.
- Gwan-gyeong.
WARNING: multiple messages have this Message-ID (diff)
From: "Mun, Gwan-gyeong" <gwan-gyeong.mun@intel.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "airlied@linux.ie" <airlied@linux.ie>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915: Fix typo in i915_drm_resume()
Date: Mon, 6 Aug 2018 06:13:05 +0000 [thread overview]
Message-ID: <251f85f6cca248b7db7289d53f984892d41c67e2.camel@intel.com> (raw)
In-Reply-To: <153332352090.15394.16477722089065680950@skylake-alporthouse-com>
On Fri, 2018-08-03 at 20:12 +0100, Chris Wilson wrote:
> Quoting Gwan-gyeong Mun (2018-08-03 17:41:50)
>
> Even for trivial patches, always include a changelog. In this case, I
> added "Trivial typo, s/loose/lose/, in i915_drm_resume."
>
> > Signed-off-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> And pushed, thanks for the spelling correction.
> -Chris
Hi Chris,
Thank you for guiding me and reviewing it.
- Gwan-gyeong.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-08-06 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 16:41 [PATCH] drm/i915: Fix typo in i915_drm_resume() Gwan-gyeong Mun
2018-08-03 16:41 ` Gwan-gyeong Mun
2018-08-03 17:30 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-08-03 18:24 ` ✓ Fi.CI.IGT: " Patchwork
2018-08-03 19:12 ` [Intel-gfx] [PATCH] " Chris Wilson
2018-08-03 19:12 ` Chris Wilson
2018-08-06 6:13 ` Mun, Gwan-gyeong [this message]
2018-08-06 6:13 ` Mun, Gwan-gyeong
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=251f85f6cca248b7db7289d53f984892d41c67e2.camel@intel.com \
--to=gwan-gyeong.mun@intel.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.