ci, on the KernelCI Slack instance
https://kernelci.slack.com/ .
Feel free to join and contribute to the conversation. The KernelCI team has
weekly calls where we also discuss the GitLab-CI pipeline.
**Acknowledgments:**
A special thanks to Nikolai Kondrashov, Tales da Aparecida - both from Red
On 2/29/24 11:34 AM, Laurent Pinchart wrote:
On Thu, Feb 29, 2024 at 11:26:51AM +0200, Nikolai Kondrashov wrote:
On 2/29/24 01:07, Laurent Pinchart wrote:
On Wed, Feb 28, 2024 at 07:55:24PM -0300, Helen Koike wrote:
**Join Our Slack Channel:**
We have a Slack channel, #gitlab-ci, on the
On 2/29/24 1:19 PM, Laurent Pinchart wrote:
On Thu, Feb 29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote:
On 2/29/24 11:34 AM, Laurent Pinchart wrote:
On Thu, Feb 29, 2024 at 11:26:51AM +0200, Nikolai Kondrashov wrote:
On 2/29/24 01:07, Laurent Pinchart wrote:
On Wed, Feb 28, 2024 at
29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote:
Of course. You're also welcome to join the #kernelci channel on libera.chat.
Isn't that a bit pointless if it's no the main IM channel ?
It *was* the original channel and still gets some usage (mostly started
by me a
Hi everyone,
On 2/29/24 11:02, Maxime Ripard wrote:
On Wed, Feb 28, 2024 at 07:55:25PM -0300, Helen Koike wrote:
Which rating would you select?
4.5 :)
One thing I'm wondering here is how we're going to cope with the
different requirements each user / framework has.
Like, Linus probably want
On 2/29/24 01:07, Laurent Pinchart wrote:
On Wed, Feb 28, 2024 at 07:55:24PM -0300, Helen Koike wrote:
**Join Our Slack Channel:**
We have a Slack channel, #gitlab-ci, on the KernelCI Slack instance
https://kernelci.slack.com/ .
Feel free to join and contribute to the conversation. The KernelCI
On 3/1/24 4:07 PM, Mark Brown wrote:
On Fri, Mar 01, 2024 at 12:27:13PM +0200, Nikolai Kondrashov wrote:
On 2/29/24 10:21 PM, Linus Torvalds wrote:
I would suggest the CI project be separate from the kernel.
It is possible to have a GitLab CI setup with the YAML files in a separate
Thanks for stopping by, Linus!
On 2/29/24 10:21 PM, Linus Torvalds wrote:
> On Thu, 29 Feb 2024 at 01:23, Nikolai Kondrashov wrote:
>>
>> However, I think a better approach would be *not* to add the .gitlab-ci.yaml
>> file in the root of the source tree, but instead chan
Check the validity of the immediately returned display clock, instead of
the functional clock already verified previously.
Signed-off-by: Nikolai Kondrashov
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/tilcdc
Hi Jarkko,
On 1/24/25 6:32 PM, Jarkko Sakkinen wrote:
> On Fri Jan 24, 2025 at 2:58 PM EET, Nikolai Kondrashov wrote:
>> Of course we could keep it outside the kernel tree. However, the point of
>> this
>> contribution is to provide kernel maintainers and developers with an
Hi Jarkko,
On 1/23/25 11:30 PM, Jarkko Sakkinen wrote:
> On Thu Jan 23, 2025 at 3:53 PM EET, Vignesh Raman wrote:
>> We are working towards creating a generic, upstream GitLab-CI pipeline
>> (kci-gitlab) that will replace DRM-CI [1]. The proposed GitLab-CI pipeline
>> is designed with a distribute
On 1/24/25 2:16 PM, Jarkko Sakkinen wrote:
> On Fri Jan 24, 2025 at 10:12 AM EET, Laurent Pinchart wrote:
>> Gitlab as an open-source software project (the community edition) is one
>> thing, but can we please avoid advertising specific proprietary services
>> in the kernel documentation ?
>
> I d
12 matches
Mail list logo
