feat: How_to_Guides: Add page on Y2K38 #51
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jsuhaas22
requested review from
StaticRocket,
cshilwant,
praneethbajjuri and
uditkumarti
as code owners
cshilwant
requested changes
Nov 26, 2024
Member
|
@jsuhaas22 Nitpick,
|
jsuhaas22
force-pushed
the
y2k38-documentation
branch
2 times, most recently
from
b2822f6 to
7bc1e97
Compare
cshilwant
requested changes
Nov 26, 2024
jsuhaas22
force-pushed
the
y2k38-documentation
branch
from
7bc1e97 to
6ff6f1a
Compare
cshilwant
previously approved these changes
Nov 26, 2024
StaticRocket
previously requested changes
Nov 26, 2024
Member
StaticRocket
left a comment
StaticRocket
left a comment
There was a problem hiding this comment.
New file does not follow common section depth [1]. Also, shouldn't AM57X be updated here as well?
[1] https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#sections
nsaulnier-ti
suggested changes
Nov 26, 2024
jsuhaas22
force-pushed
the
y2k38-documentation
branch
from
6ff6f1a to
1ca6e3f
Compare
cshilwant
requested changes
Nov 27, 2024
Member
There was a problem hiding this comment.
New file does not follow common section depth [1]
[1] https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#sections
@jsuhaas22 This comment is still not addressed in your latest changes
jsuhaas22
force-pushed
the
y2k38-documentation
branch
from
1ca6e3f to
a514eeb
Compare
|
New warnings found with rstcheck: |
jsuhaas22
force-pushed
the
y2k38-documentation
branch
from
a514eeb to
dd7544d
Compare
cshilwant
requested changes
Nov 28, 2024
Y2K38 issue has been fixed in Scarthgap, but is still present in Kirkstone, and hence also in Kirkstone images of AM335x and AM437x. Since 9.3 release is going to be a Kirkstone one, add a How_to_Guide section of the presence of this issue, and some solutions on how to deal with it. Signed-off-by: Suhaas Joshi <[email protected]>
jsuhaas22
force-pushed
the
y2k38-documentation
branch
from
dd7544d to
ea66fcf
Compare
cshilwant
approved these changes
Nov 28, 2024
StaticRocket
approved these changes
Nov 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Y2K38 issue has been fixed in Scarthgap, but is still present in Kirkstone, and hence also in Kirkstone images of AM335x and AM437x. Since 9.3 release is going to be a Kirkstone one, add a How_to_Guide warning of the presence of this issue, and some solutions on how to deal with it.