Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753492AbdGJHrP (ORCPT ); Mon, 10 Jul 2017 03:47:15 -0400 Received: from mail-it0-f68.google.com ([209.85.214.68]:35134 "EHLO mail-it0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753466AbdGJHrL (ORCPT ); Mon, 10 Jul 2017 03:47:11 -0400 MIME-Version: 1.0 X-Originating-IP: [149.6.131.75] In-Reply-To: <20170615185418.13980-1-javier@dowhile0.org> References: <20170615185418.13980-1-javier@dowhile0.org> From: Javier Martinez Canillas Date: Mon, 10 Jul 2017 09:47:05 +0200 Message-ID: Subject: Re: [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table To: Wolfram Sang Cc: Linux Kernel , Rob Herring , Javier Martinez Canillas , Florian Larysch , David Lechner , Rob Herring , Andy Shevchenko , Catalin Marinas , =?UTF-8?Q?S=C3=B6ren_Brinkmann?= , Simon Horman , Michal Simek , Dinh Nguyen , Russell King , Will Deacon , "devicetree@vger.kernel.org" , Sekhar Nori , Scott Wood , Benjamin Herrenschmidt , Joachim Eastwood , Mark Rutland , "linux-arm-kernel@lists.infradead.org" , Masahiro Yamada , Michael Ellerman , Santosh Shilimkar , Linux-Renesas , Paul Mackerras , Magnus Damm , linuxppc-dev , =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , 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: 1098 Lines: 28 Hello Wolfram, On Thu, Jun 15, 2017 at 8:54 PM, Javier Martinez Canillas wrote: > > This series is a follow-up to patch [0] that added an OF device ID table > to the at24 EEPROM driver. As you suggested [1], this version instead of > adding entries for every used tuple, only adds a single > entry for each chip type using the "atmel" vendor as a generic fallback. > > The first patch documents in the DT binding what's the correct vendor to > use and what are the ones that are being deprecated. The second one adds > the OF device ID table for the at24 driver and the next patches use this > vendor in the compatible string to each DTS that defines a compatible I2C > EEPROM device node. > > Patches can be applied independently since the DTS changes without driver > changes are no-op and the OF table won't be used without the DTS changes. > > [0]: https://lkml.org/lkml/2017/3/14/589 > [1]: https://lkml.org/lkml/2017/3/15/99 > Are you planning to pick this series? It has been in the list for months and were resent many times... Best regards, Javier