From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id 943F92FA for ; Mon, 12 May 2014 06:13:46 +0000 (UTC) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 1AC7720117 for ; Mon, 12 May 2014 06:13:45 +0000 (UTC) Date: Sun, 11 May 2014 23:13:32 -0700 From: Josh Triplett To: "H. Peter Anvin" Message-ID: <20140512061332.GA10134@thin> References: <20140511041449.GP12708@titan.lakedaemon.net> <53703416.5070400@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53703416.5070400@zytor.com> Cc: PJ Waskiewicz , Dirk Hohndel , ksummit-discuss@lists.linuxfoundation.org, Anton Arapov , Jason Cooper , Sarah A Sharp Subject: Re: [Ksummit-discuss] [TECH TOPIC] QR encoded oops for the kernel List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, May 11, 2014 at 07:38:14PM -0700, H. Peter Anvin wrote: > As valuable as I obviously believe this project is, is there actually > anything that warrants discussion at the Kernel Summit? It seems like > something to Just Do[TM]. I believe there is actually a key part of this discussion to have at Kernel Summit. We don't need to discuss the technical details of the implementation; we do need to discuss the implications of enabling mass oops-reporting, the infrastructure and information we want to include in codes valid for the next decade or so, the tradeoffs between ease of reporting and value of the reports, some potential approaches to aggregate the date, and similar. - Josh Triplett