From: Shuo Wang via lttng-dev <lttng-dev@lists.lttng.org>
To: <lttng-dev@lists.lttng.org>, <mathieu.desnoyers@efficios.com>
Cc: <hushiyuan@huawei.com>
Subject: [lttng-dev] [PATCH] README: fix typo in README.md
Date: Mon, 16 Nov 2020 20:24:46 +0800 [thread overview]
Message-ID: <20201116122446.30900-1-wangshuo47@huawei.com> (raw)
Dear Mathieu,
This mail may work.
Thank you,
Shuo
Signed-off-by: Shuo Wang <wangshuo47@huawei.com>
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 2d6dcaa..dd7ebd1 100644
--- a/README.md
+++ b/README.md
@@ -388,7 +388,7 @@ For always-on debugging self-checks:
./configure --enable-rcu-debug
For fine grained enabling of debugging self-checks, build
-urserspace-rcu with DEBUG_RCU defined and compile dependent
+userspace-rcu with DEBUG_RCU defined and compile dependent
applications with DEBUG_RCU defined when necessary.
Warning: Enabling this feature result in a performance penalty.
--
2.23.0
> Hi,
>
> This fix does not apply with "git am", probably due to the fact that the email is not
> formatted as plain text without alteration by your email client. I recommend using
> git send-email to send patches. Can you try sending it again in the proper format
> expected by git am ?
>
> You will likely find useful information about why your email client changed the
> patch formatting here:
>
> [ https://www.kernel.org/doc/html/v5.9/process/submitting-patches.html | https://www.kernel.org/doc/html/v5.9/process/submitting-patches.html ]
> [ https://www.kernel.org/doc/html/v5.9/process/email-clients.html#email-clients | https://www.kernel.org/doc/html/v5.9/process/email-clients.html#email-clients ]
>
> Thanks,
>
> Mathieu
>
> ----- On Nov 13, 2020, at 4:28 AM, wangshuo (AF) <wangshuo47 at huawei.com> wrote:
>
> > README: fix typo in README.md
>
> > Signed-off-by: Shuo Wang < [ mailto:wangshuo47 at huawei.com |
> > wangshuo47 at huawei.com ] >
>
> > ---
>
> > README.md | 2 +-
>
> > 1 file changed, 1 insertion(+), 1 deletion(-)
>
> > diff --git a/README.md b/README.md
>
> > index 2d6dcaa..dd7ebd1 100644
>
> > --- a/README.md
>
> > +++ b/README.md
>
> > @@ -388,7 +388,7 @@ For always-on debugging self-checks:
>
> > ./configure --enable-rcu-debug
>
> > For fine grained enabling of debugging self-checks, build
>
> > -urserspace-rcu with DEBUG_RCU defined and compile dependent
>
> > +userspace-rcu with DEBUG_RCU defined and compile dependent
>
> > applications with DEBUG_RCU defined when necessary.
>
> > Warning: Enabling this feature result in a performance penalty.
>
> > --
>
> > 2.23.0
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2020-11-16 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 12:24 Shuo Wang via lttng-dev [this message]
2020-11-16 14:17 ` [lttng-dev] [PATCH] README: fix typo in README.md Mathieu Desnoyers via lttng-dev
-- strict thread matches above, loose matches on Subject: below --
2020-11-13 9:28 wangshuo (AF) via lttng-dev
2020-11-13 13:30 ` Mathieu Desnoyers via lttng-dev
2020-11-13 9:01 wangshuo (AF) via lttng-dev
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=20201116122446.30900-1-wangshuo47@huawei.com \
--to=lttng-dev@lists.lttng.org \
--cc=hushiyuan@huawei.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=wangshuo47@huawei.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;
as well as URLs for NNTP newsgroup(s).