-
Notifications
You must be signed in to change notification settings - Fork 259
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where to file issues against linux-fslc? #1406
Comments
Ah, sorry. 5.15 as present in Kirkstone. |
@otavio does this mean that meta-freescale is the correct place for issues specific to linux-fslc? |
No, it is |
@jaskij, to avoid confusion. The preferred place to report issues is https://github.com/Freescale/linux-fslc as well as PRs. That said, all contribution is welcome 👍🏼 |
@otavio the problem is, I can not create an issue in that repo - the tab is not shown to me at all. That's why I started a discussion here. |
Ouch! Fixed. |
@MrCry0 merged. Can you bump the kernel? |
Merged. |
Discussed in #1404
Originally posted by jaskij February 2, 2023
I'm not sure where to go - linux-fslc has issues and discussions disabled.
I have found an issue specific to
linux-fslc
(not present in same version mainline) and have no idea where to send information about it.Noting the info down so it doesn't get lost:
add_one_port()
is called twice inlpuart_probe()
, here:https://github.com/Freescale/linux-fslc/blob/3ff5eb3ff57e665c47c072284d7f624e5452b85d/drivers/tty/serial/fsl_lpuart.c#L2965-L2986
Removing the second call seems to fix the issue (system has booted with console past the point, but I have not done extensive testing).
The text was updated successfully, but these errors were encountered: