linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@dowhile0.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Javier Martinez Canillas" <javier@dowhile0.org>,
	"Florian Larysch" <fl@n621.de>,
	"David Lechner" <david@lechnology.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Andy Shevchenko" <andy.shevchenko@gmail.com>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	"Simon Horman" <horms@verge.net.au>,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Dinh Nguyen" <dinguyen@kernel.org>,
	"Russell King" <linux@armlinux.org.uk>,
	"Will Deacon" <will.deacon@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Sekhar Nori" <nsekhar@ti.com>, "Scott Wood" <oss@buserror.net>,
	"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
	"Joachim Eastwood" <manabian@gmail.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"Masahiro Yamada" <yamada.masahiro@socionext.com>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Santosh Shilimkar" <ssantosh@kernel.org>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"Paul Mackerras" <paulus@samba.org>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"Uwe Kleine-König" <kernel@pengutronix.de>,
	"Linux I2C" <linux-i2c@vger.kernel.org>
Subject: Re: [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table
Date: Mon, 10 Jul 2017 09:47:05 +0200	[thread overview]
Message-ID: <CABxcv==J_QwoivZ0PRWMoG-weAp7F-LpEXkBxw_9jwH3ENKjsw@mail.gmail.com> (raw)
In-Reply-To: <20170615185418.13980-1-javier@dowhile0.org>

Hello Wolfram,

On Thu, Jun 15, 2017 at 8:54 PM, Javier Martinez Canillas
<javier@dowhile0.org> 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 <vendor,device> 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

  parent reply	other threads:[~2017-07-10  7:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 18:54 [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table Javier Martinez Canillas
2017-06-15 18:54 ` [RESEND PATCH v5 12/16] powerpc/5200: Add generic compatible string for I2C EEPROM Javier Martinez Canillas
2017-06-29 12:21   ` [RESEND, v5, " Michael Ellerman
2017-06-15 18:54 ` [RESEND PATCH v5 13/16] powerpc/fsl: " Javier Martinez Canillas
2017-06-29 12:21   ` [RESEND, v5, " Michael Ellerman
2017-06-15 18:54 ` [RESEND PATCH v5 14/16] powerpc/512x: " Javier Martinez Canillas
2017-06-29 12:21   ` [RESEND, v5, " Michael Ellerman
2017-06-15 18:54 ` [RESEND PATCH v5 15/16] powerpc/83xx: " Javier Martinez Canillas
2017-06-29 12:21   ` [RESEND, v5, " Michael Ellerman
2017-06-15 18:54 ` [RESEND PATCH v5 16/16] powerpc/44x: " Javier Martinez Canillas
2017-06-29 12:21   ` [RESEND, v5, " Michael Ellerman
2017-07-10  7:47 ` Javier Martinez Canillas [this message]
2017-07-31 15:30 ` [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table Wolfram Sang
2017-07-31 16:17   ` Javier Martinez Canillas
2017-08-28 16:01     ` Wolfram Sang
2017-08-29  8:44       ` Javier Martinez Canillas
2017-08-29  8:48         ` Wolfram Sang
2017-08-30 16:19           ` Javier Martinez Canillas
2017-08-30 17:42             ` Wolfram Sang
2017-08-30 19:57               ` Javier Martinez Canillas
2017-08-30 20:15                 ` Geert Uytterhoeven
2017-08-30 20:59                   ` Javier Martinez Canillas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABxcv==J_QwoivZ0PRWMoG-weAp7F-LpEXkBxw_9jwH3ENKjsw@mail.gmail.com' \
    --to=javier@dowhile0.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=catalin.marinas@arm.com \
    --cc=david@lechnology.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=fl@n621.de \
    --cc=horms@verge.net.au \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=magnus.damm@gmail.com \
    --cc=manabian@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=mpe@ellerman.id.au \
    --cc=nsekhar@ti.com \
    --cc=oss@buserror.net \
    --cc=paulus@samba.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=soren.brinkmann@xilinx.com \
    --cc=ssantosh@kernel.org \
    --cc=will.deacon@arm.com \
    --cc=wsa@the-dreams.de \
    --cc=yamada.masahiro@socionext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).