From: Mark Brown <broonie@kernel.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lkp] [PATCH v4 3/5] mfd: tps65912: Add driver for the TPS65912 PMIC
Date: Fri, 2 Oct 2015 14:47:58 +0100 [thread overview]
Message-ID: <20151002134758.GP12635@sirena.org.uk> (raw)
In-Reply-To: <20151002133212.GA18604@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Fri, Oct 02, 2015 at 09:32:12PM +0800, Fengguang Wu wrote:
> On Fri, Oct 02, 2015 at 10:58:59AM +0100, Mark Brown wrote:
> > > 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 >>):
Ah, I see - it's more clear in the warnings only case, it's less obvious
in the errors case that this message would be different if there were
only warnings.
> 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.
That would be excellent, yes.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-10-02 13:48 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 20:37 [PATCH v4 0/5] mfd: tps65912: Driver rewrite with DT support Andrew F. Davis
2015-10-01 20:37 ` Andrew F. Davis
2015-10-01 20:37 ` [PATCH v4 1/5] Documentation: tps65912: Add DT bindings for the TPS65912 PMIC Andrew F. Davis
2015-10-01 20:37 ` Andrew F. Davis
2015-10-01 20:37 ` [PATCH v4 2/5] mfd: tps65912: Remove old driver in preparation for new driver Andrew F. Davis
2015-10-01 20:37 ` Andrew F. Davis
2015-10-05 9:28 ` Lee Jones
2015-10-05 9:29 ` Lee Jones
2015-10-05 9:29 ` Lee Jones
2015-10-05 16:01 ` Andrew F. Davis
2015-10-05 16:01 ` Andrew F. Davis
2015-10-01 20:37 ` [PATCH v4 3/5] mfd: tps65912: Add driver for the TPS65912 PMIC Andrew F. Davis
2015-10-01 20:37 ` Andrew F. Davis
[not found] ` <1443731874-21362-4-git-send-email-afd-l0cyMroinI0@public.gmane.org>
2015-10-01 20:51 ` kbuild test robot
2015-10-01 20:51 ` kbuild test robot
[not found] ` <20151002095859.GN12635@sirena.org.uk>
2015-10-02 13:32 ` [lkp] " Fengguang Wu
2015-10-02 13:47 ` Mark Brown [this message]
2015-10-01 20:57 ` kbuild test robot
2015-10-01 20:57 ` kbuild test robot
2015-10-01 20:57 ` kbuild test robot
2015-10-01 20:57 ` kbuild test robot
2015-10-01 23:49 ` Andrew F. Davis
2015-10-01 23:49 ` Andrew F. Davis
2015-10-05 9:24 ` Lee Jones
2015-10-05 9:27 ` Lee Jones
2015-10-12 15:06 ` Andrew F. Davis
2015-10-12 15:06 ` Andrew F. Davis
[not found] ` <561BCC8A.3090402-l0cyMroinI0@public.gmane.org>
2015-10-13 7:34 ` Lee Jones
2015-10-13 7:34 ` Lee Jones
2015-10-01 20:37 ` [PATCH v4 4/5] regulator: tps65912: Add regulator " Andrew F. Davis
2015-10-01 20:37 ` Andrew F. Davis
2015-10-02 19:21 ` Grygorii Strashko
2015-10-02 19:21 ` Grygorii Strashko
2015-10-22 16:47 ` Mark Brown
[not found] ` <20151022164724.GZ8232-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-10-23 12:46 ` Andrew F. Davis
2015-10-23 12:46 ` Andrew F. Davis
2015-10-23 23:18 ` Mark Brown
2015-10-24 0:11 ` Andrew F. Davis
2015-10-24 0:11 ` Andrew F. Davis
[not found] ` <562ACCCC.503-l0cyMroinI0@public.gmane.org>
2015-10-24 22:14 ` Mark Brown
2015-10-24 22:14 ` Mark Brown
[not found] ` <20151024221457.GS29919-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-10-25 20:45 ` Andrew F. Davis
2015-10-25 20:45 ` Andrew F. Davis
[not found] ` <562D3F77.5040205-l0cyMroinI0@public.gmane.org>
2015-10-26 0:43 ` Mark Brown
2015-10-26 0:43 ` Mark Brown
2015-10-26 15:47 ` Andrew F. Davis
2015-10-26 15:47 ` Andrew F. Davis
[not found] ` <562E4B1D.4060205-l0cyMroinI0@public.gmane.org>
2015-10-27 0:16 ` Mark Brown
2015-10-27 0:16 ` Mark Brown
[not found] ` <20151027001608.GJ28319-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-10-27 14:23 ` Andrew F. Davis
2015-10-27 14:23 ` Andrew F. Davis
2015-11-04 15:35 ` Andrew F. Davis
2015-11-04 15:35 ` Andrew F. Davis
2015-11-05 10:14 ` Mark Brown
2015-11-05 18:04 ` Andrew F. Davis
2015-11-05 18:04 ` Andrew F. Davis
2015-11-06 10:43 ` Mark Brown
2015-11-06 18:10 ` Andrew F. Davis
2015-11-06 18:10 ` Andrew F. Davis
2015-11-06 21:16 ` Mark Brown
[not found] ` <20151106211651.GJ18409-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-11-09 17:41 ` Andrew F. Davis
2015-11-09 17:41 ` Andrew F. Davis
2015-11-10 9:57 ` Mark Brown
2015-11-10 16:47 ` Andrew F. Davis
2015-11-10 16:47 ` Andrew F. Davis
2015-11-10 17:04 ` Mark Brown
2015-11-10 17:52 ` Andrew F. Davis
2015-11-10 17:52 ` Andrew F. Davis
2015-11-10 18:44 ` Mark Brown
2015-11-10 19:40 ` Andrew F. Davis
2015-11-10 19:40 ` Andrew F. Davis
[not found] ` <56424836.7000608-l0cyMroinI0@public.gmane.org>
2015-11-16 18:23 ` Mark Brown
2015-11-16 18:23 ` Mark Brown
2015-10-01 20:37 ` [PATCH v4 5/5] gpio: tps65912: Add GPIO " Andrew F. Davis
2015-10-01 20:37 ` Andrew F. Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151002134758.GP12635@sirena.org.uk \
--to=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.