From: Shuah Khan <skhan@linuxfoundation.org>
To: Randy Dunlap <rdunlap@infradead.org>, corbet@lwn.net
Cc: sshefali021@gmail.com, kstewart@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2] docs: add workload-tracing document to admin-guide
Date: Mon, 30 Jan 2023 16:20:31 -0700 [thread overview]
Message-ID: <68594f1d-25e3-4eab-98cb-8691d01719c7@linuxfoundation.org> (raw)
In-Reply-To: <25089707-b037-4cce-367b-819ddd239b17@infradead.org>
On 1/27/23 22:40, Randy Dunlap wrote:
> Hi--
>
> On 1/27/23 15:46, Shuah Khan wrote:
>> Add a new section to the admin-guide with information of interest to
>> application developers and system integrators doing analysis of the
>> Linux kernel for safety critical applications.
>>
>> This section will contain documents supporting analysis of kernel
>> interactions with applications, and key kernel subsystems expectations.
>>
>> Add a new workload-tracing document to this new section.
>>
>> Signed-off-by: Shefali Sharma <sshefali021@gmail.com>
>> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
>> ---
>> Changes since v1:
>> - Addressed review comments on v1 on long lines, rst syntax, license
>>
>> Documentation/admin-guide/index.rst | 11 +
>> .../admin-guide/workload-tracing.rst | 591 ++++++++++++++++++
>> 2 files changed, 602 insertions(+)
>> create mode 100644 Documentation/admin-guide/workload-tracing.rst
>>
>
Thank you for the review. I will send v3 to address them.
thanks,
-- Shuah
next prev parent reply other threads:[~2023-01-30 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 23:46 Shuah Khan
2023-01-28 3:14 ` Bagas Sanjaya
2023-01-30 23:19 ` Shuah Khan
2023-01-28 5:40 ` Randy Dunlap
2023-01-30 23:20 ` Shuah Khan [this message]
2023-01-28 8:35 ` Thorsten Leemhuis
2023-01-30 23:30 ` Shuah Khan
2023-01-30 23:52 ` Jonathan Corbet
2023-01-31 19:20 ` Shuah Khan
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=68594f1d-25e3-4eab-98cb-8691d01719c7@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sshefali021@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 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®