From: Bo Liu <liubo03@inspur.com>
To: <jani.nikula@linux.intel.com>, <joonas.lahtinen@linux.intel.com>,
<rodrigo.vivi@intel.com>, <tvrtko.ursulin@linux.intel.com>,
<airlied@linux.ie>, <daniel@ffwll.ch>
Cc: <intel-gfx@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
Bo Liu <liubo03@inspur.com>
Subject: [PATCH] drm/i915: Fix double word in comments
Date: Thu, 22 Sep 2022 04:36:01 -0400 [thread overview]
Message-ID: <20220922083601.3236-1-liubo03@inspur.com> (raw)
Remove the repeated word "not" in comments.
Signed-off-by: Bo Liu <liubo03@inspur.com>
---
drivers/gpu/drm/i915/display/intel_bw.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
index 4ace026b29bd..a5cb253f6dc5 100644
--- a/drivers/gpu/drm/i915/display/intel_bw.c
+++ b/drivers/gpu/drm/i915/display/intel_bw.c
@@ -646,7 +646,7 @@ static unsigned int intel_bw_crtc_num_active_planes(const struct intel_crtc_stat
{
/*
* We assume cursors are small enough
- * to not not cause bandwidth problems.
+ * to not cause bandwidth problems.
*/
return hweight8(crtc_state->active_planes & ~BIT(PLANE_CURSOR));
}
@@ -661,7 +661,7 @@ static unsigned int intel_bw_crtc_data_rate(const struct intel_crtc_state *crtc_
for_each_plane_id_on_crtc(crtc, plane_id) {
/*
* We assume cursors are small enough
- * to not not cause bandwidth problems.
+ * to not cause bandwidth problems.
*/
if (plane_id == PLANE_CURSOR)
continue;
--
2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: Bo Liu <liubo03@inspur.com>
To: <jani.nikula@linux.intel.com>, <joonas.lahtinen@linux.intel.com>,
<rodrigo.vivi@intel.com>, <tvrtko.ursulin@linux.intel.com>,
<airlied@linux.ie>, <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, Bo Liu <liubo03@inspur.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [PATCH] drm/i915: Fix double word in comments
Date: Thu, 22 Sep 2022 04:36:01 -0400 [thread overview]
Message-ID: <20220922083601.3236-1-liubo03@inspur.com> (raw)
Remove the repeated word "not" in comments.
Signed-off-by: Bo Liu <liubo03@inspur.com>
---
drivers/gpu/drm/i915/display/intel_bw.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
index 4ace026b29bd..a5cb253f6dc5 100644
--- a/drivers/gpu/drm/i915/display/intel_bw.c
+++ b/drivers/gpu/drm/i915/display/intel_bw.c
@@ -646,7 +646,7 @@ static unsigned int intel_bw_crtc_num_active_planes(const struct intel_crtc_stat
{
/*
* We assume cursors are small enough
- * to not not cause bandwidth problems.
+ * to not cause bandwidth problems.
*/
return hweight8(crtc_state->active_planes & ~BIT(PLANE_CURSOR));
}
@@ -661,7 +661,7 @@ static unsigned int intel_bw_crtc_data_rate(const struct intel_crtc_state *crtc_
for_each_plane_id_on_crtc(crtc, plane_id) {
/*
* We assume cursors are small enough
- * to not not cause bandwidth problems.
+ * to not cause bandwidth problems.
*/
if (plane_id == PLANE_CURSOR)
continue;
--
2.27.0
WARNING: multiple messages have this Message-ID (diff)
From: Bo Liu <liubo03@inspur.com>
To: <jani.nikula@linux.intel.com>, <joonas.lahtinen@linux.intel.com>,
<rodrigo.vivi@intel.com>, <tvrtko.ursulin@linux.intel.com>,
<airlied@linux.ie>, <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, Bo Liu <liubo03@inspur.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH] drm/i915: Fix double word in comments
Date: Thu, 22 Sep 2022 04:36:01 -0400 [thread overview]
Message-ID: <20220922083601.3236-1-liubo03@inspur.com> (raw)
Remove the repeated word "not" in comments.
Signed-off-by: Bo Liu <liubo03@inspur.com>
---
drivers/gpu/drm/i915/display/intel_bw.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
index 4ace026b29bd..a5cb253f6dc5 100644
--- a/drivers/gpu/drm/i915/display/intel_bw.c
+++ b/drivers/gpu/drm/i915/display/intel_bw.c
@@ -646,7 +646,7 @@ static unsigned int intel_bw_crtc_num_active_planes(const struct intel_crtc_stat
{
/*
* We assume cursors are small enough
- * to not not cause bandwidth problems.
+ * to not cause bandwidth problems.
*/
return hweight8(crtc_state->active_planes & ~BIT(PLANE_CURSOR));
}
@@ -661,7 +661,7 @@ static unsigned int intel_bw_crtc_data_rate(const struct intel_crtc_state *crtc_
for_each_plane_id_on_crtc(crtc, plane_id) {
/*
* We assume cursors are small enough
- * to not not cause bandwidth problems.
+ * to not cause bandwidth problems.
*/
if (plane_id == PLANE_CURSOR)
continue;
--
2.27.0
next reply other threads:[~2022-09-22 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 8:36 Bo Liu [this message]
2022-09-22 8:36 ` [Intel-gfx] [PATCH] drm/i915: Fix double word in comments Bo Liu
2022-09-22 8:36 ` Bo Liu
2022-09-22 17:14 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning for " Patchwork
2022-09-22 17:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: " Patchwork
2022-09-22 17:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-22 22:02 ` [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=20220922083601.3236-1-liubo03@inspur.com \
--to=liubo03@inspur.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.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.