All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: kernelci@groups.io, wangmy@cn.fujitsu.com
Subject: Re: help: how to contribute to the community
Date: Thu, 10 Dec 2020 10:12:41 +0000	[thread overview]
Message-ID: <ec96708e-12d5-ff21-1f21-dfd2262927dc@collabora.com> (raw)
In-Reply-To: <a34a999c78584e0e9953360bbd5797f8@G08CNEXMBPEKD05.g08.fujitsu.local>

On 08/12/2020 07:43, Wang Mingyu wrote:
> Hi, all
> 
> I am currently using this tool. 
> Although I am still new, I still want to contribute to the community. 
> Is there anything I can do？
> For example, bug fix, or simple new plan to kernelci.

Thank you for your interest, there are plenty of things that
first-time contributors can do in KernelCI.  One would be to
enable i386 builds with Clang, as per this GitHub issue:

  https://github.com/kernelci/kernelci-core/issues/517

At the moment, kernelci.org builds linux-next with Clang on arm,
arm64, x86_64 and riscv architectures.  Of all the other
architectures that aren't built yet, i386 should be the easiest
one to add.  Doing this does not require any service to be
installed locally, all you need is Docker and the kernelci-core
repository.  The work to do is basically:

* run kci_build in KernelCI Docker images with the clang-11 and
  clang-10 toolchains to build kernels for i386

* report or fix any build issues, this might just work but it
  needs to be verified with both clang versions

* edit build-configs.yaml to add i386 to the list of
  architectures built with clang-11 and clang-10 if it also
  works

* verify that the list of builds for linux-next includes i386
  defconfig with clang using "kci_build list_kernel_configs"

* send a pull request in GitHub with the change, this will then
  get tested on staging.kernelci.org and reviewed

If it works as expected on staging.kernelci.org and once the PR
review is complete, this will then get merged and deployed in
production for kernelci.org.

Does that sound like something you would be interested to do?

Thanks,
Guillaume

  reply	other threads:[~2020-12-10 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08  7:43 help: how to contribute to the community Wang Mingyu
2020-12-10 10:12 ` Guillaume Tucker [this message]
2020-12-11  2:15   ` Wang Mingyu
2021-01-06  1:05   ` Wang Mingyu
2021-01-25 23:21     ` Guillaume Tucker
2021-01-26  5:36       ` Wang Mingyu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ec96708e-12d5-ff21-1f21-dfd2262927dc@collabora.com \
    --to=guillaume.tucker@collabora.com \
    --cc=kernelci@groups.io \
    --cc=wangmy@cn.fujitsu.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.