From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751080AbbJBTUJ (ORCPT ); Fri, 2 Oct 2015 15:20:09 -0400 Received: from mail-ob0-f178.google.com ([209.85.214.178]:35005 "EHLO mail-ob0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750843AbbJBTUG (ORCPT ); Fri, 2 Oct 2015 15:20:06 -0400 MIME-Version: 1.0 From: "Luis R. Rodriguez" Date: Fri, 2 Oct 2015 12:19:45 -0700 X-Google-Sender-Auth: Vd23DVqkDynC36-L3_07STXaTdI Message-ID: Subject: Wiki for automatic reports / fixes To: Fengguang Wu , Valentin Rothberg , Dan Carpenter , Mel Gorman , Steven Rostedt Cc: Johannes Thumshirn , Konstantin Ryabitsev , Jonathan Corbet , Lars Kurth , Ian Jackson , Stefano Stabellini , Vitaly Kuznetsov , Robert Schweikert , ms@suse.de, Juergen Gross , "linux-kernel@vger.kernel.org" , Joerg Roedel , "linux-doc@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Fengguang, Dan, Mel, Valentin has some open source tools that uses some SAT solver the backend to hunt for dead, the undertaker tool [0] inspects Kconfig, and uses SAT solver to do this work. A while ago it was determined that this code could not be merged upstream for a variety of reasons, but mostly due to the fact that it was R&D work and it was under GPLv3 [1]. I know a few of you have other testing tools which helps find other sorts of issues. To my knowledge automated reports for these may be expected readily these days by developers from 0-day bot, and for smatch issues, but its unclear what we should expect from the other ones. There is also some pending ideas over a few of these other testing frameworks, for instance a recent discussion was started to evaluate the potential for integration of Xen into the 0-day bot testing scheme. While discussing expectations and information about reports over these with Valentin it occurred to me information about all these may be scattered separately and some developers may be surprised when they first get reports / fixes from these sorts of testing systems and that perhaps it may be useful if we had a single wiki entry point where we could refer folks to the different ongoing testing infrastructures out there working upstream. If we could piggy back off of an already existing wiki then great, but if not I was thinking something off of wiki.kernel.org might be good. How about tests.wiki.kernel.org ? If such projects don't have a wiki they could perhaps use pages off of tests.wiki.kernel.org to elaborate and set expectations straight. Thoughts? [0] http://vamos.informatik.uni-erlangen.de/trac/undertake [1] https://lwn.net/Articles/617383/ Luis