Skip to content

Conversation

@kprosise
Copy link
Contributor

@kprosise kprosise commented May 8, 2025

Emulation with QEMU moved from Getting Started to User Guide alongside the other QEMU pages. QEMU command made to match.
Other QEMU pages edited to have one parameter per line for the command example so as to match; this makes sense as it can be easier to visually parse.

QA Steps: Built HTML with no issues or warnings. Checked rendered output. Edited with linter plugin on.

This commit addresses issue FFTK-4004, "Align QEMU pages"

PR Template and Checklist

Please complete as much as possible to speed up the reviewing process.

Readiness and adding reviewers as appropriate is required.

All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.

Readiness

  • Merge (pending reviews)

Overview

--

Checklist

  • Run spelling and grammar check, preferably with linter.
  • Avoid changing any header associated with a link/reference.
  • Step through instructions (or ask someone to do so).
  • Review for wordiness
  • Match tone and style of page/section.
  • Run make linkcheck.
  • View HTML in a browser to check rendering.
  • Use semantic newlines.
  • follow best practices for commits.
    • Descriptive title written in the imperative.
    • Include brief overview of QA steps taken.
    • Mention any related issues numbers.
    • End message with sign off/DCO line (-s, --signoff).
    • Sign commit with your gpg key (-S, --gpg-sign).
    • Squash commits if needed.
  • Request PR review by a technical writer and at least one peer.

Comments

Changes considered but ruled out for the time being:

  • image name: 'Emulation with QEMU' tutorial page and the QEMU pages have different image names, however this is noted on the qemu pages, and depends upon if the prebuilt Target is used
  • Use of an include for the shared command in the tutorial: The use of include in the docs is being reevaluated as it prevents the PDF version from rendering correctly.

@kprosise kprosise requested review from angolini and vanmaegima May 8, 2025 14:27
:maxdepth: 1

x86_64
emulation-with-qemu
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a benefit on keeping this page? Since it was introduced, it seems a bit redundant for me, I may be missing some detail there.

I think the note about QEMU in https://ci.foundries.io/projects/fio-docs/builds/2912/docs/artifacts/html/getting-started/flash-device/index.html#prerequisites-and-pre-work pointing directly to the QEMU general pages will do the work.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am more than okay with removing it!

@kprosise kprosise force-pushed the align-qemu-pages branch from 14f9f5b to 9dd7d5d Compare May 12, 2025 12:57
Emulation with QEMU page deleted, as it does not serve much of a
purpose.
Other QEMU pages edited to have one parameter per line for the command
example; this is so it can be easier to visually parse.

QA Steps: Built HTML with no issues or warnings. Checked rendered
output. Edited with linter plugin on.

This commit addresses issue FFTK-4004, "Align QEMU pages"

Signed-off-by: Katrina Prosise <katrina.prosise@foundries.io>
@kprosise kprosise force-pushed the align-qemu-pages branch from 9dd7d5d to 87f71ed Compare May 12, 2025 13:52
Copy link
Member

@vanmaegima vanmaegima left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kprosise kprosise merged commit abb84cf into foundriesio:main May 12, 2025
2 of 3 checks passed
@kprosise kprosise deleted the align-qemu-pages branch May 12, 2025 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants