Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754869AbbG3LIp (ORCPT ); Thu, 30 Jul 2015 07:08:45 -0400 Received: from mail-wi0-f180.google.com ([209.85.212.180]:36041 "EHLO mail-wi0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753558AbbG3LIo (ORCPT ); Thu, 30 Jul 2015 07:08:44 -0400 Date: Thu, 30 Jul 2015 12:08:38 +0100 From: Lee Jones To: Matt Fleming Cc: Wim Van Sebroeck , linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org, Mika Westerberg , Andy Shevchenko , Jean Delvare , Wolfram Sang , Matt Fleming , Peter Tyser , Samuel Ortiz , Zha Qipeng , Guenter Roeck Subject: Re: [PATCH v2 1/3] iTCO_wdt: Expose watchdog properties using platform data Message-ID: <20150730110838.GE14642@x1> References: <1438171844-24861-1-git-send-email-matt@codeblueprint.co.uk> <1438171844-24861-2-git-send-email-matt@codeblueprint.co.uk> <20150729153556.GC9319@x1> <20150729163953.GI2773@codeblueprint.co.uk> <20150730085347.GF9319@x1> <20150730091458.GB2704@codeblueprint.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150730091458.GB2704@codeblueprint.co.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2148 Lines: 52 On Thu, 30 Jul 2015, Matt Fleming wrote: > On Thu, 30 Jul, at 09:53:47AM, Lee Jones wrote: > > On Wed, 29 Jul 2015, Matt Fleming wrote: > > > > > On Wed, 29 Jul, at 04:35:56PM, Lee Jones wrote: > > > > > > > > For my own reference (I assume this will go through the MFD tree): > > > > Acked-by: Lee Jones > > > > > > Great, thanks Lee! > > > > > > I've no strong opinion on which tree these 3 patches go through but at > > > the very least patches 1 and 2 need to go through the same tree to avoid > > > build breakage (since PATCH 1 introduces 'struct itco_wdt_platform_data' > > > which is used in PATCH 2). > > > > > > For reference, the other patches are here, > > > > > > https://lkml.kernel.org/r/1438171844-24861-3-git-send-email-matt@codeblueprint.co.uk > > > https://lkml.kernel.org/r/1438171844-24861-4-git-send-email-matt@codeblueprint.co.uk > > > > Obviously this makes things more difficult. Once you have the other > > Acks you need, I suggest you re-submit the set using --threaded, so we > > can all see what's going on. > > Umm... I submitted *this* version using --threaded. In fact, that's > plain to see from the Message-Id format in the links above. It's just > that I only Cc'd you on the patch that touched the mfd code. Ah yes, similar result. Again, unless the set is particularlly large or touches many subsystems, I tend to Cc all affected Maintainers (if I'm sending, or like to be Cc'ed if I'm the recipient) on all of the patches. Set status is much easier to track that way and issues which might be relevant to more than one patch in the set can be seen by all. > I can resubmit with the Ack/Review tags and copy you on the whole series > if you'd like. That would be perfect. -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/