From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755507AbbESLBY (ORCPT <rfc822;w@1wt.eu>);
	Tue, 19 May 2015 07:01:24 -0400
Received: from mail-la0-f43.google.com ([209.85.215.43]:32792 "EHLO
	mail-la0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754400AbbESLBW (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 19 May 2015 07:01:22 -0400
Date: Tue, 19 May 2015 13:01:19 +0200
From: Johan Hovold <johan@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Johan Hovold <johan@kernel.org>, Lee Jones <lee.jones@linaro.org>,
        Support Opensource <support.opensource@diasemi.com>,
        Samuel Ortiz <sameo@linux.intel.com>,
        Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org,
        Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
        Milo Kim <milo.kim@ti.com>, patches@opensource.wolfsonmicro.com,
        Fabio Estevam <fabio.estevam@freescale.com>,
        Marek Szyprowski <m.szyprowski@samsung.com>,
        stable <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] mfd: da9052: fix broken regulator probe
Message-ID: <20150519110119.GN28127@localhost>
References: <20150513172936.GE2761@sirena.org.uk>
 <20150514071943.GA20358@x1>
 <20150515144739.GC13976@localhost>
 <20150518091049.GN22418@x1>
 <20150518095159.GB28127@localhost>
 <20150518162405.GA2761@sirena.org.uk>
 <20150518164630.GL28127@localhost>
 <20150518184654.GC2761@sirena.org.uk>
 <20150519100103.GM28127@localhost>
 <20150519103808.GE2761@sirena.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150519103808.GE2761@sirena.org.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, May 19, 2015 at 11:38:08AM +0100, Mark Brown wrote:
> On Tue, May 19, 2015 at 12:01:03PM +0200, Johan Hovold wrote:
> 
> > I might have read too much into that response, but the pings were hardly
> > contentless (they all included the commit message and some the full patch).
> 
> It's the new content that is important here - if it boils down to "have
> you looked at this yet" that's not really adding anything and if it's a
> patch to be applied then it really needs to not be quoted.

My reminders sent directly to you explicitly mentioned it being a
regression every time. That should trigger a maintainer's interest
enough to look at the quoted context or ask for a resend.

How should a patch submitter know that you simply drop mails with an mfd
prefix even if it's directed to you? Unless documented somewhere, that's
were Lee can help through being familiar with the quirks of your work flow.

Johan