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=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=unavailable 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 E18EFC4360F for ; Wed, 20 Mar 2019 06:28:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B07E021850 for ; Wed, 20 Mar 2019 06:28:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1553063309; bh=q6Tl8p2X/rd5nPI6ZuGwZIG2VMWqvkZUQ3AmxOiHGqs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=uWHgz2+YWAiirkbhTQGyDyhZXWjT1VQc51F+PryBGzO/fFmWy8H1mDYQaMhBuGzlb gBkn+0s22PNEtPZ6YJZWSxN4jxJQULX6b3X9LWFrTcqq7y9gCfJ0Qjt1qduF3x2XLp dAZanZwKf2lOC0kBTL/kDmOheNqDclpKc8ZOgPU8= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727679AbfCTG22 (ORCPT ); Wed, 20 Mar 2019 02:28:28 -0400 Received: from mail.kernel.org ([198.145.29.99]:40846 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727452AbfCTG22 (ORCPT ); Wed, 20 Mar 2019 02:28:28 -0400 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CAD752184E; Wed, 20 Mar 2019 06:28:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1553063307; bh=q6Tl8p2X/rd5nPI6ZuGwZIG2VMWqvkZUQ3AmxOiHGqs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Hy2IuyxDTqyNO86MzHtCQRsYBqm+0SqWn1v35q0bJnaub/HMuIapUVQj9mhSDtyRp O4yuN4G37XsHqbIcV6f+bUa20jPHvgnOqxjSfpbZI3UAaAY3fliJ/2gnTu7/5DRz3I +cX44XzmOP4hxx4xtsOzOwT0U0FeKzIDTxpDQcJw= Date: Wed, 20 Mar 2019 07:28:24 +0100 From: Greg KH To: Jon Masters Cc: Sasha Levin , Amir Goldstein , Steve French , lsf-pc@lists.linux-foundation.org, linux-fsdevel , linux-mm , LKML , "Luis R. Rodriguez" Subject: Re: [LSF/MM TOPIC] FS, MM, and stable trees Message-ID: <20190320062824.GA11080@kroah.com> References: <20190213073707.GA2875@kroah.com> <20190213091803.GA2308@kroah.com> <20190213192512.GH69686@sasha-vm> <20190213195232.GA10047@kroah.com> <79d10599-70d2-7d06-1cee-6e52d36233bf@jonmasters.org> <20190320050659.GA16580@kroah.com> <134e0fe1-e468-5243-90b5-ccb81d63e9a1@jonmasters.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <134e0fe1-e468-5243-90b5-ccb81d63e9a1@jonmasters.org> User-Agent: Mutt/1.11.4 (2019-03-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 20, 2019 at 02:14:09AM -0400, Jon Masters wrote: > On 3/20/19 1:06 AM, Greg KH wrote: > > On Tue, Mar 19, 2019 at 11:46:09PM -0400, Jon Masters wrote: > >> On 2/13/19 2:52 PM, Greg KH wrote: > >>> On Wed, Feb 13, 2019 at 02:25:12PM -0500, Sasha Levin wrote: > >> > >>>> So really, it sounds like a low hanging fruit: we don't really need to > >>>> write much more testing code code nor do we have to refactor existing > >>>> test suites. We just need to make sure the right tests are running on > >>>> stable kernels. I really want to clarify what each subsystem sees as > >>>> "sufficient" (and have that documented somewhere). > >>> > >>> kernel.ci and 0-day and Linaro are starting to add the fs and mm tests > >>> to their test suites to address these issues (I think 0-day already has > >>> many of them). So this is happening, but not quite obvious. I know I > >>> keep asking Linaro about this :( > >> > >> We're working on investments for LDCG[0] in 2019 that include kernel CI > >> changes for server use cases. Please keep us informed of what you folks > >> ultimately want to see, and I'll pass on to the steering committee too. > >> > >> Ultimately I've been pushing for a kernel 0-day project for Arm. That's > >> probably going to require a lot of duplicated effort since the original > >> 0-day project isn't open, but creating an open one could help everyone. > > > > Why are you trying to duplicate it on your own? That's what kernel.ci > > should be doing, please join in and invest in that instead. It's an > > open source project with its own governance and needs sponsors, why > > waste time and money doing it all on your own? > > To clarify, I'm pushing for investment in kernel.ci to achieve that goal > that it could provide the same 0-day capability for Arm and others. Great, that's what I was trying to suggest :) > It'll ultimately result in duplicated effort vs if 0-day were open. "Half" of 0-day is open, but it's that other half that is still needed... thanks, greg k-h