From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org
Subject: [PATCH 5/5] ia64: kernel: perfmon_m*.h: delete duplicated words
Date: Sat, 25 Jul 2020 17:40:13 -0700 [thread overview]
Message-ID: <20200726004013.20534-6-rdunlap@infradead.org> (raw)
In-Reply-To: <20200726004013.20534-1-rdunlap@infradead.org>
Delete the repeated word "the" in two places.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: linux-ia64@vger.kernel.org
---
arch/ia64/kernel/perfmon_mckinley.h | 2 +-
arch/ia64/kernel/perfmon_montecito.h | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20200720.orig/arch/ia64/kernel/perfmon_mckinley.h
+++ linux-next-20200720/arch/ia64/kernel/perfmon_mckinley.h
@@ -92,7 +92,7 @@ pfm_mck_pmc_check(struct task_struct *ta
/*
* we must clear the debug registers if pmc13 has a value which enable
* memory pipeline event constraints. In this case we need to clear the
- * the debug registers if they have not yet been accessed. This is required
+ * debug registers if they have not yet been accessed. This is required
* to avoid picking stale state.
* PMC13 is "active" if:
* one of the pmc13.cfg_dbrpXX field is different from 0x3
--- linux-next-20200720.orig/arch/ia64/kernel/perfmon_montecito.h
+++ linux-next-20200720/arch/ia64/kernel/perfmon_montecito.h
@@ -174,7 +174,7 @@ pfm_mont_pmc_check(struct task_struct *t
/*
* we must clear the debug registers if pmc41 has a value which enable
* memory pipeline event constraints. In this case we need to clear the
- * the debug registers if they have not yet been accessed. This is required
+ * debug registers if they have not yet been accessed. This is required
* to avoid picking stale state.
* PMC41 is "active" if:
* one of the pmc41.cfg_dtagXX field is different from 0x3
prev parent reply other threads:[~2020-07-26 0:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 0:40 [PATCH 0/5] ia64: " Randy Dunlap
2020-07-26 0:40 ` [PATCH 1/5] ia64: pal.h: delete duplicated word Randy Dunlap
2020-07-26 0:40 ` [PATCH 2/5] ia64: perfmon.h: " Randy Dunlap
2020-07-26 0:40 ` [PATCH 3/5] ia64: spinlock.h: " Randy Dunlap
2020-07-26 0:40 ` [PATCH 4/5] ia64: uv: uv_hub.h: " Randy Dunlap
2020-07-26 0:40 ` Randy Dunlap [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=20200726004013.20534-6-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@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
all inboxes | Powered by JetHome®