From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jiang Jian <jiangjian@cdjrlc.com>, airlied@linux.ie, daniel@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Jiang Jian <jiangjian@cdjrlc.com>,
rodrigo.vivi@intel.com
Subject: Re: [Intel-gfx] [PATCH] GPU: drm: i915: drop unexpected word 'for' in comments
Date: Thu, 23 Jun 2022 20:00:11 +0300 [thread overview]
Message-ID: <871qvfnwmc.fsf@intel.com> (raw)
In-Reply-To: <20220623101113.28470-1-jiangjian@cdjrlc.com>
On Thu, 23 Jun 2022, Jiang Jian <jiangjian@cdjrlc.com> wrote:
> there is an unexpected word 'for' in the comments that need to be dropped
While it's also unexpected, it's really *duplicated* word.
> file - drivers/gpu/drm/i915/i915_reg.h
> line - 2537
>
> * Please check the detailed lore in the commit message for for experimental
>
> changed to:
>
> * Please check the detailed lore in the commit message for experimental
>
The above is just duplication of the patch itself, and completely
unnecessary.
The patch subject prefix should be something like "drm/i915:" or
"drm/i915/reg:".
Pro-tip for figuring out good guesses of what the subject prefix should
be:
$ git log --since={5-year} --no-merges --pretty=format:%s -- drivers/gpu/drm/i915/i915_reg.h | sed 's/:.*//' | sort | uniq -c | sort -rn | head
312 drm/i915
113 drm/i915/icl
57 drm/i915/tgl
26 drm/i915/cnl
25 drm/i915/display
22 drm/i915/dg2
16 drm/i915/psr
14 drm/i915/gt
14 drm/i915/adl_p
12 drm/i915/dg1
The patch itself is fine, but I'm nitpicking on the commit message
because I've seen lots of patches like this, with the same kind of stuff
in the commit messages.
BR,
Jani.
> Signed-off-by: Jiang Jian <jiangjian@cdjrlc.com>
> ---
> drivers/gpu/drm/i915/i915_reg.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 616164fa2e32..738c020396af 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -2534,7 +2534,7 @@
> * HDMI/DP bits are g4x+
> *
> * WARNING: Bspec for hpd status bits on gen4 seems to be completely confused.
> - * Please check the detailed lore in the commit message for for experimental
> + * Please check the detailed lore in the commit message for experimental
> * evidence.
> */
> /* Bspec says GM45 should match G4X/VLV/CHV, but reality disagrees */
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jiang Jian <jiangjian@cdjrlc.com>, airlied@linux.ie, daniel@ffwll.ch
Cc: tvrtko.ursulin@linux.intel.com, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Jiang Jian <jiangjian@cdjrlc.com>,
rodrigo.vivi@intel.com
Subject: Re: [PATCH] GPU: drm: i915: drop unexpected word 'for' in comments
Date: Thu, 23 Jun 2022 20:00:11 +0300 [thread overview]
Message-ID: <871qvfnwmc.fsf@intel.com> (raw)
In-Reply-To: <20220623101113.28470-1-jiangjian@cdjrlc.com>
On Thu, 23 Jun 2022, Jiang Jian <jiangjian@cdjrlc.com> wrote:
> there is an unexpected word 'for' in the comments that need to be dropped
While it's also unexpected, it's really *duplicated* word.
> file - drivers/gpu/drm/i915/i915_reg.h
> line - 2537
>
> * Please check the detailed lore in the commit message for for experimental
>
> changed to:
>
> * Please check the detailed lore in the commit message for experimental
>
The above is just duplication of the patch itself, and completely
unnecessary.
The patch subject prefix should be something like "drm/i915:" or
"drm/i915/reg:".
Pro-tip for figuring out good guesses of what the subject prefix should
be:
$ git log --since={5-year} --no-merges --pretty=format:%s -- drivers/gpu/drm/i915/i915_reg.h | sed 's/:.*//' | sort | uniq -c | sort -rn | head
312 drm/i915
113 drm/i915/icl
57 drm/i915/tgl
26 drm/i915/cnl
25 drm/i915/display
22 drm/i915/dg2
16 drm/i915/psr
14 drm/i915/gt
14 drm/i915/adl_p
12 drm/i915/dg1
The patch itself is fine, but I'm nitpicking on the commit message
because I've seen lots of patches like this, with the same kind of stuff
in the commit messages.
BR,
Jani.
> Signed-off-by: Jiang Jian <jiangjian@cdjrlc.com>
> ---
> drivers/gpu/drm/i915/i915_reg.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 616164fa2e32..738c020396af 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -2534,7 +2534,7 @@
> * HDMI/DP bits are g4x+
> *
> * WARNING: Bspec for hpd status bits on gen4 seems to be completely confused.
> - * Please check the detailed lore in the commit message for for experimental
> + * Please check the detailed lore in the commit message for experimental
> * evidence.
> */
> /* Bspec says GM45 should match G4X/VLV/CHV, but reality disagrees */
--
Jani Nikula, Intel Open Source Graphics Center
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jiang Jian <jiangjian@cdjrlc.com>, airlied@linux.ie, daniel@ffwll.ch
Cc: joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
tvrtko.ursulin@linux.intel.com, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Jiang Jian <jiangjian@cdjrlc.com>
Subject: Re: [PATCH] GPU: drm: i915: drop unexpected word 'for' in comments
Date: Thu, 23 Jun 2022 20:00:11 +0300 [thread overview]
Message-ID: <871qvfnwmc.fsf@intel.com> (raw)
In-Reply-To: <20220623101113.28470-1-jiangjian@cdjrlc.com>
On Thu, 23 Jun 2022, Jiang Jian <jiangjian@cdjrlc.com> wrote:
> there is an unexpected word 'for' in the comments that need to be dropped
While it's also unexpected, it's really *duplicated* word.
> file - drivers/gpu/drm/i915/i915_reg.h
> line - 2537
>
> * Please check the detailed lore in the commit message for for experimental
>
> changed to:
>
> * Please check the detailed lore in the commit message for experimental
>
The above is just duplication of the patch itself, and completely
unnecessary.
The patch subject prefix should be something like "drm/i915:" or
"drm/i915/reg:".
Pro-tip for figuring out good guesses of what the subject prefix should
be:
$ git log --since={5-year} --no-merges --pretty=format:%s -- drivers/gpu/drm/i915/i915_reg.h | sed 's/:.*//' | sort | uniq -c | sort -rn | head
312 drm/i915
113 drm/i915/icl
57 drm/i915/tgl
26 drm/i915/cnl
25 drm/i915/display
22 drm/i915/dg2
16 drm/i915/psr
14 drm/i915/gt
14 drm/i915/adl_p
12 drm/i915/dg1
The patch itself is fine, but I'm nitpicking on the commit message
because I've seen lots of patches like this, with the same kind of stuff
in the commit messages.
BR,
Jani.
> Signed-off-by: Jiang Jian <jiangjian@cdjrlc.com>
> ---
> drivers/gpu/drm/i915/i915_reg.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 616164fa2e32..738c020396af 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -2534,7 +2534,7 @@
> * HDMI/DP bits are g4x+
> *
> * WARNING: Bspec for hpd status bits on gen4 seems to be completely confused.
> - * Please check the detailed lore in the commit message for for experimental
> + * Please check the detailed lore in the commit message for experimental
> * evidence.
> */
> /* Bspec says GM45 should match G4X/VLV/CHV, but reality disagrees */
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-06-23 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 10:11 [PATCH] GPU: drm: i915: drop unexpected word 'for' in comments Jiang Jian
2022-06-23 10:11 ` Jiang Jian
2022-06-23 17:00 ` Jani Nikula [this message]
2022-06-23 17:00 ` Jani Nikula
2022-06-23 17:00 ` Jani Nikula
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=871qvfnwmc.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jiangjian@cdjrlc.com \
--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.