From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753520AbbJBNcY (ORCPT ); Fri, 2 Oct 2015 09:32:24 -0400 Received: from mga11.intel.com ([192.55.52.93]:15019 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752795AbbJBNcV (ORCPT ); Fri, 2 Oct 2015 09:32:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,623,1437462000"; d="scan'208";a="782741396" Date: Fri, 2 Oct 2015 21:32:12 +0800 From: Fengguang Wu To: Mark Brown Cc: LKML Subject: Re: [lkp] [PATCH v4 3/5] mfd: tps65912: Add driver for the TPS65912 PMIC Message-ID: <20151002133212.GA18604@wfg-t540p.sh.intel.com> References: <1443731874-21362-4-git-send-email-afd@ti.com> <201510020451.0XYHKQyq%fengguang.wu@intel.com> <20151002095859.GN12635@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151002095859.GN12635@sirena.org.uk> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [CC LKML] On Fri, Oct 02, 2015 at 10:58:59AM +0100, Mark Brown wrote: > On Fri, Oct 02, 2015 at 04:51:11AM +0800, kbuild test robot wrote: > > Hi Andrew, > > > > [auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore] > > > > config: x86_64-allmodconfig (attached as .config) > > reproduce: > > git checkout d617dea974adf7dc262f2d49dea24a673e0403e2 > > # save the attached .config to linux build tree > > make ARCH=x86_64 > > > > All error/warnings (new ones prefixed by >>): > > It would be good if somewhere early on in these mails the report said if > the build failed - that's key information about how urgent issues are > and it's not always clear if things are errors or warnings. When the robot say "All error/warnings" it has build failure (and possibly warnings). If there are only build warnings it'll say All warnings (new ones prefixed by >>): Would you like making that line more clear, or show the info earlier in the email body or even email title? For example, the first line could be changed to [auto build test ERROR on v4.3-rc3 -- if it's inappropriate base, please ignore] [auto build test WARNING on v4.3-rc3 -- if it's inappropriate base, please ignore] depending on whether it has build failure or just warnings. Thanks, Fengguang