Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753566AbdGJIe6 (ORCPT ); Mon, 10 Jul 2017 04:34:58 -0400 Received: from mail-it0-f66.google.com ([209.85.214.66]:35701 "EHLO mail-it0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752679AbdGJIez (ORCPT ); Mon, 10 Jul 2017 04:34:55 -0400 MIME-Version: 1.0 X-Originating-IP: [149.6.131.75] In-Reply-To: <20170710080712.3oyktu3pjdbgxx7k@dell> References: <20170615184928.12007-1-javier@dowhile0.org> <20170710080712.3oyktu3pjdbgxx7k@dell> From: Javier Martinez Canillas Date: Mon, 10 Jul 2017 10:34:54 +0200 Message-ID: Subject: Re: [RESEND PATCH v6 0/8] mfd: Add OF device table to I2C drivers that are missing it To: Lee Jones Cc: Linux Kernel , "devicetree@vger.kernel.org" , Wolfram Sang , Rob Herring , Tony Lindgren , Aaro Koskinen , =?UTF-8?Q?Beno=C3=AEt_Cousson?= , Linus Walleij , Mark Rutland , "linux-omap@vger.kernel.org" , Russell King , "linux-arm-kernel@lists.infradead.org" , Linux I2C Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2107 Lines: 54 On Mon, Jul 10, 2017 at 10:07 AM, Lee Jones wrote: > On Mon, 10 Jul 2017, Javier Martinez Canillas wrote: > >> Hello Lee, >> >> On Thu, Jun 15, 2017 at 8:49 PM, Javier Martinez Canillas >> wrote: >> > >> > This series add OF device ID tables to mfd I2C drivers whose devices are >> > either used in Device Tree source files or are listed in binding docs as >> > a compatible string. >> > >> > That's done because the plan is to change the I2C core to report proper OF >> > modaliases instead of always reporting a MODALIAS=i2c: regardless if >> > a device was registered via DT or using the legacy platform data mechanism. >> > >> > So these patches will make sure that mfd I2C drivers modules will continue >> > to be autoloaded once the I2C core is changed to report proper OF modalias. >> > >> > Users didn't have a vendor prefix in the used compatible strings, but since >> > there wasn't a DT binding document for these drivers, it can be said that >> > were working for mere luck and so this series fixes the users and add a DT >> > binding doc for the drivers. >> > >> > Most patches can be applied independently, with the exception of patches >> > 2 to 4 that should be applied in the same tree to keep bisect-ability. I >> > suggest these to go through the MFD subsystem tree. >> > >> > Best regards, >> > Javier >> > >> >> Are you planning to pick this series? It has been in the list for >> months and were resent many times... > > I think you exaggerate a little. Your last Ack (from Linus) was only > collected in v6, which has only been resent once with that Ack > applied. =:) > You are right, sorry for the impatience. > We are currently only half way through the merge-window. This patch > will be hoovered up during the early -rcs. Please be patient around > the time of the merge-window, since Maintainers are either usually > very busy with pull-requests, or taking a 2 minute breather before > the chaos starts over. > Great, I just was worried that it could fell through the cracks. Thanks for your answer. Best regards, Javier