docs: ftrace: Fix minor issues in the doc
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 0 repliesNew
Changes since PATCH v1 from the cover letter
- Improves the redaction as per Randy suggestion.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | docs: ftrace: Clarify the RAM impact of buffer_size_kbDocumentation/ | +2 | 0 replies | |
| 2/3 | docs: ftrace: Fix typosDocumentation/ | +3 | 0 replies | |
| 3/3 | docs: ftrace: Fix small notation mistakeDocumentation/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] docs: ftrace: Fix minor issues in the doc
I didn't want to be pushy with these minor fixes but occur to me now that, even all seem to be clear in the latest version of the RFC (v2) related to these fixes, a clean patchset could be expected after such RFC. So here we go:
Clarifies the RAM footprint of buffer_size_kb without getting into implementation details.
Fix typos and a small notation mistakes in the doc.
Changes since PATCH v1:
- Improves the redaction as per Randy suggestion.
Changes since RFC v2:
- Take out the notation mistake into its own commit because it is not a typo.
Changes since RFC v1:
- Removes implementation description of the RAM footprint of buffer_size_kb, but still make the corresponded clarification.
- Removes a patch that was just for illustration purposes because Steven already got the issue that I was referring to.
- Adds a patch to fix other typos in the doc.
Frank A. Cancio Bello (3):
docs: ftrace: Clarify the RAM impact of buffer_size_kb
docs: ftrace: Fix typos
docs: ftrace: Fix small notation mistake
Documentation/trace/ftrace.rst | 9 +++++---- Documentation/trace/ring-buffer-design.txt | 2 +- 2 files changed, 6 insertions(+), 5 deletions(-)
Signature · 1 line
2.17.1