Skip to content

Conversation

@deborahbrouwer
Copy link
Contributor

This MR makes it clear that upstream contributions can go right to mailing lists.

As suggested by @dakr and @dwlsalmeida in #52

@ojeda could you please review?

Currently the upstream development process for Tyr suggests that a
developer could open a merge request for review and discussion in
the panfrost-linux repository on Freedesktop GitLab.

While merge requests can still be a useful collaboration tool, other DRM
developers might not be reading those merge requests, so to be absolutely
clear, just direct new upstream contributions to the mailing lists.

Signed-off-by: Deborah Brouwer <[email protected]>
@ojeda
Copy link
Member

ojeda commented Dec 31, 2025

It sounded to me like @dwlsalmeida was saying that MRs to the prototype would now have a specific purpose (i.e. doing testing that requires a working driver).

If that is the case, i.e. if downstream/prototype development is not expected to be common anymore, then perhaps the page should be reorganized a bit?

But maybe I misinterpreted what he meant.

Happy new year!

Comment on lines +86 to +87
To work on any given task, assign it to yourself. For patches targeting the downstream
staging branch, open a merge request against `tyr-dev`.
Copy link
Member

@ojeda ojeda Dec 31, 2025

Choose a reason for hiding this comment

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

I would suggest mentioning the upstream route too or removing both, instead of mentioning only the downstream case (the text before the change has both too).

(But please see my comment above)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants