Closed johnfial closed 1 year ago
@johnfial - I think the "new" files under the Linux RN have to be "put" into the draft ones, isn't it? I'm referring to the in-tree files and qatlib file. Also (I just realized about them), the revision_history_dc and revision_history_lac files which are used for the API manuals have to be excluded, they are under /doc.
For your first point -- are you talking about the files at documentation PR 43?
For your second point (API Ref rev_histories), you are correct, thy should be invisible by default. However, it's easily correctable, but if I don't do it on this PR, it's no major concern because that information is already in the current public API Ref Manual PDFs. Good catch, though!
@johnfial - I think the "new" files under the Linux RN have to be "put" into the draft ones, isn't it? I'm referring to the in-tree files and qatlib file. Also (I just realized about them), the revision_history_dc and revision_history_lac files which are used for the API manuals have to be excluded, they are under /doc.
For your first point -- are you talking about the files at documentation PR 43?
For your second point (API Ref rev_histories), you are correct, thy should be invisible by default. However, it's easily correctable, but if I don't do it on this PR, it's no major concern because that information is already in the current public API Ref Manual PDFs. Good catch, though!
I'm referring to the files added in documentation PR 12:
I'm referring to the files added in documentation PR 12:
- in_tree_firmware_RN.rst
- in_tree_kernel_driver_RN.rst
- qatlib_RN.rst
Great catch. I removed these drafts and will rename them on the source repo. However, I don't consider the contents sensitive enough to warrant a "rebase" or removal of this whole PR.
@jdschuet could you kindly review this PR?
@jdschuet videos were removed yesterday