linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: zhumao001@208suo.com
To: fbarrat@linux.ibm.com, ajd@linux.ibm.com, arnd@arndb.de,
	gregkh@linuxfoundation.org
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH] cxl/ocxl: Possible repeated word
Date: Sun, 18 Jun 2023 23:08:19 +0800	[thread overview]
Message-ID: <787f5a712a0459bc21d83bb388770b58@208suo.com> (raw)
In-Reply-To: <20230618150648.1123-1-dengshaomin@cdjrlc.com>

[-- Attachment #1: Type: text/plain, Size: 777 bytes --]


Delete repeated word in comment.

Signed-off-by: Zhu Mao <zhumao001@208suo.com>
---
  drivers/misc/cxl/native.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/misc/cxl/native.c b/drivers/misc/cxl/native.c
index 50b0c44bb8d7..6957946a6463 100644
--- a/drivers/misc/cxl/native.c
+++ b/drivers/misc/cxl/native.c
@@ -920,7 +920,7 @@ int cxl_attach_dedicated_process_psl9(struct 
cxl_context *ctx, u64 wed, u64 amr)
       * Ideally we should do a wmb() here to make sure the changes to 
the
       * PE are visible to the card before we call afu_enable.
       * On ppc64 though all mmios are preceded by a 'sync' instruction 
hence
-     * we dont dont need one here.
+     * we dont need one here.
       */

      result = cxl_ops->afu_reset(afu);

[-- Attachment #2: Type: text/html, Size: 1328 bytes --]

       reply	other threads:[~2023-06-19  0:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230618150648.1123-1-dengshaomin@cdjrlc.com>
2023-06-18 15:08 ` zhumao001 [this message]
2023-06-20  7:43   ` [PATCH] cxl/ocxl: Possible repeated word Frederic Barrat
2023-06-20 12:18   ` Michael Ellerman

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=787f5a712a0459bc21d83bb388770b58@208suo.com \
    --to=zhumao001@208suo.com \
    --cc=ajd@linux.ibm.com \
    --cc=arnd@arndb.de \
    --cc=fbarrat@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).