Skip to content
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

Request to host linux-mediatek mailinglist #134

Open
mbgg opened this issue Nov 12, 2021 · 6 comments
Open

Request to host linux-mediatek mailinglist #134

mbgg opened this issue Nov 12, 2021 · 6 comments

Comments

@mbgg
Copy link

mbgg commented Nov 12, 2021

Hi,

I would love to see the linux-mediatek mailinglist being hosted at patchew.org
You can subscribe to the list here:
https://lists.infradead.org/mailman/listinfo/linux-mediatek

If possible I'd like to have compile tests enabled. If that's fine for you I'd need to know what kind of container you use for the tests to provide a script to test-compile the kernel.

Thanks for your consideration!
Matthias

@famz
Copy link
Collaborator

famz commented Feb 14, 2022

Now I'm working on a new importer script, I will also look into adding all LKML patches to patchew.org.

For tests, the recommended way is to integrated CI from gitlab.com or github.com, but I know that is not straightforward for kernel. So maybe it should be the other way around: let me know your test requirements and I can see if we can meet it. Docker based would be ideal.

@bonzini
Copy link
Contributor

bonzini commented Feb 14, 2022

@dcaratti is running tests using GitHub CI I think, is that correct?

@dcaratti
Copy link
Contributor

@dcaratti is running tests using GitHub CI I think, is that correct?

for MPTCP we are running Cirrus CI triggered by a webhook on the github repo. The only limitation is, github doesn't support push options. So, to avoid re-running the CI for every message that is in-reply-to a patch that has been already imported, we applied the following workaround:

diff --git a/patchew-cli b/patchew-cli
index 9472554..4a7adb9 100755
--- a/patchew-cli
+++ b/patchew-cli
@@ -977,7 +977,7 @@ class ApplyCommand(SubCommand):
             print("No series need apply")
             return 3
         logf = tempfile.NamedTemporaryFile(mode="w+", encoding="utf-8")
-        push_repo = toapply.get("git.push_to")
+        push_repo = None if 'ci.skip' in str(toapply.get('git.push_options')) else toapply.get("git.push_to")
         public_repo = toapply.get("git.public_repo")
         wd = tempfile.mkdtemp(dir="/var/tmp")
         try:

@bonzini
Copy link
Contributor

bonzini commented Feb 22, 2022

Hi, you can already get LKML patches via something like https://patchew.org/search?q=project:linux+to:linux-mediatek, but it's a bit slow so we can certainly have a separate subscription for linux-mediatek as well!

Alternatively, we could create you an account that lets you have a "watched search", which in your case would be something like project:linux to:linux-mediatek not:merged. Let me know what you prefer!

@famz
Copy link
Collaborator

famz commented Feb 22, 2022

I also notice another problem, which is, for example, not all patches on linux-mptcp has linux-kernel@ in the Cc so they don't get indexed by the main LKML public-inbox...

I'm not sure what's the Cc practice on linux-mediatek.

@mbgg
Copy link
Author

mbgg commented May 17, 2022

@famz sorry for the very late answer. It's common practice to add linux-mediatek as Cc on mails but not necessarly LKML so it would be great to have them added seperately.

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

No branches or pull requests

4 participants