From: "Hunt, David" <david.hunt@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, john.mcnamara@intel.com, marko.kovacevic@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] doc: rework vm power manager user guide
Date: Mon, 17 Feb 2020 10:44:44 +0000 [thread overview]
Message-ID: <26d21fec-6100-e315-5d16-3efe9ca0628b@intel.com> (raw)
In-Reply-To: <3090513.CAdn2TfLgq@xps>
Hi Thomas,
On 16/2/2020 11:13 AM, Thomas Monjalon wrote:
> 07/01/2020 10:13, David Hunt:
>> Review and re-work of vm_power_manager documentation. Hopefully this
>> is clearer, easier to follow.
>>
>> Signed-off-by: David Hunt <david.hunt@intel.com>
> checkpatch is reporting a typo done several times:
> s/virutal/virtual/
Initially, my checkpatch was clean, I even upgraded to using 5.5.4
kernel, still no hits using checkpatch. It was only when I installed the
codespell package that I finally saw the typos. New revision coming soon.
>> ---
>> .../img/vm_power_mgr_highlevel.svg | 2189 +++++++++++------
> This high-level diagram is nice but I disagree about having text blocks.
> I think images should be image-only and the text can be in .rst.
> It will be easier to update.
>
Good suggestion, I have the rework done, will post soon.
Thanks,
Dave.
next prev parent reply other threads:[~2020-02-17 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 9:13 David Hunt
2020-02-16 11:13 ` Thomas Monjalon
2020-02-17 10:44 ` Hunt, David [this message]
2020-02-17 10:48 ` [dpdk-dev] [PATCH v2] " David Hunt
2020-02-21 18:02 ` Thomas Monjalon
2020-02-25 16:46 ` Ferruh Yigit
2020-02-25 16:59 ` Thomas Monjalon
2020-02-25 17:47 ` Thomas Monjalon
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=26d21fec-6100-e315-5d16-3efe9ca0628b@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=thomas@monjalon.net \
/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).