public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com>
To: kernelci@groups.io, santiago.esteban@microchip.com,
	Guillaume Tucker <guillaume.tucker@collabora.com>
Subject: Re: KCIDB contribuition #KCIDB
Date: Mon, 22 Feb 2021 11:41:20 +0200	[thread overview]
Message-ID: <5d6fbc94-bdfd-9822-3bb0-0502751294b0@redhat.com> (raw)
In-Reply-To: <a91111f8-158d-f811-5309-feb6571d3412@microchip.com>

Hello Santiago,

On 2/22/21 10:02 AM, Santiago.Esteban via info via groups.io wrote:
> Good morning KernelCI, Nikolai,
> 
> As I mention here before, I work at Microchip, and we are building a
> test farm based on Labgrid which currently, allow us to test Linux
> kernels in several ARM SoC devices (Cortex-A5, ARM9 variants). We would
> like to contribute to KernelCI effort with our builds/tests but support
> for non Lava external labs is not available yet.
> 
> Therefore, It seems that KCIDB is the place for us. We would like to
> start contributing our builds/tests to this project.
> 
> As part of our current efforts, we have build a local instance of the
> KernelCI infrastructure. I've already asked Nicolai @DevConf, but here,
> at a wider audience, Are there any tool that allows to submmit
> "standard" KernelCI formatted data into the KCIDB database?

I suppose if you already drive everything with an instance of KernelCI
infrastructure, you can just use the KCIDB interface code that was merged
there. However, I think Guillaume would be able to help you better here.

Guillaume, do you think that would work?

> Best regards,
> 
> Santiago Esteban
> 
> ps. Nikolai, I liked a lot your presentation @DevConf, it helped me to
> understand some aspect of KernelCI  and KCIDB to me.

Ah, glad to hear that, thanks :)

Nick


  reply	other threads:[~2021-02-22  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  8:02 KCIDB contribuition #KCIDB Santiago.Esteban via info
2021-02-22  9:41 ` Nikolai Kondrashov [this message]
2021-02-22 10:25   ` Guillaume Tucker
2021-02-22 10:31     ` Nikolai Kondrashov
2021-02-24  9:42       ` Santiago.Esteban via info
2021-02-24  9:51         ` Nikolai Kondrashov
2021-02-24  9:29     ` Santiago.Esteban via info

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=5d6fbc94-bdfd-9822-3bb0-0502751294b0@redhat.com \
    --to=nikolai.kondrashov@redhat.com \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernelci@groups.io \
    --cc=santiago.esteban@microchip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox