From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 38F46C47255 for ; Mon, 11 May 2020 12:38:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 07FD7206D6 for ; Mon, 11 May 2020 12:38:51 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="OFF3sLET" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729674AbgEKMiu (ORCPT ); Mon, 11 May 2020 08:38:50 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:20000 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729343AbgEKMiu (ORCPT ); Mon, 11 May 2020 08:38:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1589200729; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=JgWXktU2LOpwxkLtvpr3LpJKXrfJg+c2CFwjM1G4yBY=; b=OFF3sLETBXtNNidUyKBPHl1brN2JTh1qlZGD+4PiFGabbOSRiLbEPc4WDoZJpNkOSIbGqM Vf6UVF6tD7SB5pJn72EQrWBaNYXyj5J+G0PdpJiecAU44of9b9/MyubHOOIT+saJZuX+vh s8HfefSkU9G703LLK8qSCCnlwUv1r+k= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-308-43ZrKMCENkW46GwLcRho9w-1; Mon, 11 May 2020 08:38:47 -0400 X-MC-Unique: 43ZrKMCENkW46GwLcRho9w-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id D3AA0835B44; Mon, 11 May 2020 12:38:46 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id CAD766C77F; Mon, 11 May 2020 12:38:46 +0000 (UTC) Received: from zmail19.collab.prod.int.phx2.redhat.com (zmail19.collab.prod.int.phx2.redhat.com [10.5.83.22]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id B6E244E560; Mon, 11 May 2020 12:38:46 +0000 (UTC) Date: Mon, 11 May 2020 08:38:46 -0400 (EDT) From: Veronika Kabatova To: bpf , ast@kernel.org Cc: brouer@redhat.com, Jiri Benc , Jiri Olsa , Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= , Stanislav Kozina Message-ID: <1556585430.22389743.1589200726419.JavaMail.zimbra@redhat.com> In-Reply-To: <330319358.22380533.1589199587680.JavaMail.zimbra@redhat.com> Subject: Mailing list for CI results MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.40.195.236, 10.4.195.8] Thread-Topic: Mailing list for CI results Thread-Index: /sDt1vbCBqMGp1T1xlgTkQMtWyXp+w== X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: bpf-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: bpf@vger.kernel.org Hello, we've been discussing CI for bpf-next in previous meetings. One of the action items from there was a creation of a separate mailing list purely for CI results, to not pollute the regular development list. Is there already a list created? If not, can it be done? We'd be interested in sending out some examples to get early feedback before the testing is enabled. Please let me know if I should reach out to someone else for this. I'll attend this weeks office hours to discuss other CI action items. Thanks, Veronika