From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 0/9] Improve Linux drivers GSG section
Date: Wed, 16 Mar 2022 18:41:21 +0100 [thread overview]
Message-ID: <5190484.GXAFRqVoOG@thomas> (raw)
In-Reply-To: <20220316134551.1099599-1-bruce.richardson@intel.com>
16/03/2022 14:45, Bruce Richardson:
> This patchset reworks large parts of the linux drivers section of the
> Linux Getting Started Guide, so as to make it clearer and easier to
> read. The overall flow of the page is adjusted so that more important
> information is nearer the top, and so that all information on VFIO is
> consolidated into a single section. In terms of the content of the
> sections, there are some minor changes to adjust what is a warning vs
> just a "note" in the doc, and there are some updates to increase
> emphasis on VFIO ovs UIO.
>
> Including stable on CC for the set, as all patches may be candidates for
> backport to help improve docs for older releases too.
>
> V2:
> * Rebased on top of main, now that other doc patches are applied
> * Reworded commit titles to use "doc:" prefix
>
> Bruce Richardson (9):
> doc: replace special characters for (R) symbol in Linux GSG
> doc: fix missing note on UIO module in Linux GSG
> doc: make UIO safety warning more visible in Linux GSG
> doc: move section on binding drivers up the page in GSG
> doc: emphasise VFIO over UIO-based modules in GSG
> doc: split GSG VFIO section into subsections
> doc: move GSG section on UIO to the end of drivers page
> doc: consolidate all VFIO content on GSG driver page
> doc: change informational warnings to notes in Linux GSG
Except for the first 2 patches, I think it is not mandatory to backport,
so I've removed the tag Cc:stable.
Applied, thanks.
prev parent reply other threads:[~2022-03-16 17:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 17:22 [PATCH 0/9] Improve linux " Bruce Richardson
2022-03-02 17:22 ` [PATCH 1/9] doc/linux_gsg: replace special characters for (R) symbol Bruce Richardson
2022-03-02 17:22 ` [PATCH 2/9] doc/linux_gsg: fix missing note on UIO module Bruce Richardson
2022-03-02 17:22 ` [PATCH 3/9] doc/linux_gsg: make UIO safety warning more visible Bruce Richardson
2022-03-02 17:22 ` [PATCH 4/9] doc/linux_gsg: move section on binding drivers up the page Bruce Richardson
2022-03-02 17:22 ` [PATCH 5/9] doc/linux_gsg: emphasise VFIO over UIO-based modules Bruce Richardson
2022-03-02 17:22 ` [PATCH 6/9] doc/linux_gsg: split VFIO section into subsections Bruce Richardson
2022-03-02 17:22 ` [PATCH 7/9] doc/linux_gsg: move UIO section to the end Bruce Richardson
2022-03-02 17:22 ` [PATCH 8/9] doc/linux_gsg: consolidate all VFIO content Bruce Richardson
2022-03-02 17:22 ` [PATCH 9/9] doc/linux_gsg: change informational warnings to notes Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 0/9] Improve Linux drivers GSG section Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 1/9] doc: replace special characters for (R) symbol in Linux GSG Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 2/9] doc: fix missing note on UIO module " Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 3/9] doc: make UIO safety warning more visible " Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 4/9] doc: move section on binding drivers up the page in GSG Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 5/9] doc: emphasise VFIO over UIO-based modules " Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 6/9] doc: split GSG VFIO section into subsections Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 7/9] doc: move GSG section on UIO to the end of drivers page Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 8/9] doc: consolidate all VFIO content on GSG driver page Bruce Richardson
2022-03-16 13:45 ` [PATCH v2 9/9] doc: change informational warnings to notes in Linux GSG Bruce Richardson
2022-03-16 17:41 ` Thomas Monjalon [this message]
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=5190484.GXAFRqVoOG@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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).