From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758600AbbGQP37 (ORCPT ); Fri, 17 Jul 2015 11:29:59 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:43343 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757395AbbGQP36 (ORCPT ); Fri, 17 Jul 2015 11:29:58 -0400 Date: Fri, 17 Jul 2015 16:29:55 +0100 From: Nariman Poushin To: Mark Brown Cc: Stephen Rothwell , Lee Jones , Liam Girdwood , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Richard Fitzgerald , Charles Keepax Subject: Re: linux-next: build warnings after merge of the regmap tree Message-ID: <20150717152955.GI21939@opensource.wolfsonmicro.com> References: <20150717143934.4f0ce5d7@canb.auug.org.au> <20150717094436.GC21939@opensource.wolfsonmicro.com> <20150717103450.GJ11162@sirena.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150717103450.GJ11162@sirena.org.uk> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 17, 2015 at 11:34:50AM +0100, Mark Brown wrote: > On Fri, Jul 17, 2015 at 10:44:36AM +0100, Nariman Poushin wrote: > > > What is the best course of action here? I am more than happy to help with > > whatever is needed but unsure of the etiquette here and also not sure > > what I can do. > > > Clearly there are some clients that need updating but they were not > > present in the regmap tree, so is the correct thing to do to merge > > in the mfd and sound-asoc tree and provide a fixup commit? > > > Just let me know and I am happy to do whatever is deemed correct. > > Please send patches fixing the problems you have introduced. I have sent the patches to fix the build errors you found Stephen. Just wanted to let you guys know I will be on vacation for 1 week, so if there are any issues they might not be addressed until then. Thanks Nariman