From: Markus Elfring <Markus.Elfring@web.de>
To: yangliuxm34@gmail.com, kernel-janitors@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, liuyang34@xiaomi.com,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] trace: code optimization
Date: Thu, 9 Jan 2020 14:16:46 +0100 [thread overview]
Message-ID: <4f4bed1d-9dc0-0665-4b61-8afc9ebf8201@web.de> (raw)
In-Reply-To: <27225bf0ec9b4e2f3d313456aee75e294361d550.1578561009.git.liuyang34@xiaomi.com>
> use scnprintf instead of snprinr and no need to check
Will a typo be avoided in the final change description?
> Signed-off-by: liuyang34 …
Will this information need also an adjustment for the desired specification
of a real name?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=b07f636fca1c8fbba124b0082487c0b3890a0e0c#n458
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: yangliuxm34@gmail.com, kernel-janitors@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, liuyang34@xiaomi.com,
Ingo Molnar <mingo@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] trace: code optimization
Date: Thu, 09 Jan 2020 13:16:46 +0000 [thread overview]
Message-ID: <4f4bed1d-9dc0-0665-4b61-8afc9ebf8201@web.de> (raw)
In-Reply-To: <27225bf0ec9b4e2f3d313456aee75e294361d550.1578561009.git.liuyang34@xiaomi.com>
> use scnprintf instead of snprinr and no need to check
Will a typo be avoided in the final change description?
> Signed-off-by: liuyang34 …
Will this information need also an adjustment for the desired specification
of a real name?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=b07f636fca1c8fbba124b0082487c0b3890a0e0c#n458
Regards,
Markus
next prev parent reply other threads:[~2020-01-09 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1578561009.git.liuyang34@xiaomi.com>
2020-01-09 9:12 ` [PATCH] trace: code optimization liuyang34
2020-01-10 0:57 ` [RESEND PATCH] " liuyang34
2020-01-09 13:16 ` Markus Elfring [this message]
2020-01-09 13:16 ` [PATCH] " Markus Elfring
2020-01-09 14:32 ` Steven Rostedt
2020-01-09 14:32 ` Steven Rostedt
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=4f4bed1d-9dc0-0665-4b61-8afc9ebf8201@web.de \
--to=markus.elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyang34@xiaomi.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=yangliuxm34@gmail.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.