mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: pangzizhen001@208suo.com
To: hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Fwd: [PATCH] s390/kernel: Fix comment typo
Date: Wed, 12 Jul 2023 17:40:11 +0800	[thread overview]
Message-ID: <24163a6fd52a3a496a27740039e07dd7@208suo.com> (raw)
In-Reply-To: <20230712093757.36116-1-wangjianli@cdjrlc.com>

Delete duplicate word "the"

Signed-off-by: wangjianli <wangjianli@cdjrlc.com>
---
  arch/s390/kernel/perf_cpum_sf.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/s390/kernel/perf_cpum_sf.c 
b/arch/s390/kernel/perf_cpum_sf.c
index 06efad5b4f93..3e1d8c58e4d1 100644
--- a/arch/s390/kernel/perf_cpum_sf.c
+++ b/arch/s390/kernel/perf_cpum_sf.c
@@ -1193,7 +1193,7 @@ static void perf_event_count_update(struct 
perf_event *event, u64 count)
   * combined-sampling data entry consists of a basic- and a 
diagnostic-sampling
   * data entry.    The sampling function is determined by the flags in 
the perf
   * event hardware structure.  The function always works with a 
combined-sampling
- * data entry but ignores the the diagnostic portion if it is not 
available.
+ * data entry but ignores the diagnostic portion if it is not 
available.
   *
   * Note that the implementation focuses on basic-sampling data entries 
and, if
   * such an entry is not valid, the entire combined-sampling data entry 
is

       reply	other threads:[~2023-07-12  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230712093757.36116-1-wangjianli@cdjrlc.com>
2023-07-12  9:40 ` pangzizhen001 [this message]
2023-07-18 16:34   ` pangzizhen001
     [not found] <20230712094239.16048-1-wangjianli@cdjrlc.com>
2023-07-12  9:45 ` Fwd: " pangzizhen001

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=24163a6fd52a3a496a27740039e07dd7@208suo.com \
    --to=pangzizhen001@208suo.com \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    /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®