Linux I2C development
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: linux-kernel@vger.kernel.org, "Rob Herring" <robh@kernel.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, "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
Subject: Re: [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table
Date: Mon, 31 Jul 2017 17:30:09 +0200	[thread overview]
Message-ID: <20170731153009.xkjknygpmckv2pfp@ninjato> (raw)
In-Reply-To: <20170615185418.13980-1-javier@dowhile0.org>

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]


> 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.

But there is a dependency, no? If I apply the driver patch,
non-converted device trees will not find their eeproms anymore. So, I
need to wait until all DTS patches are upstream, right? I can pick patch
1, though. We can already document it.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-07-31 15:30 UTC|newest]

Thread overview: 13+ 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 02/16] " Javier Martinez Canillas
2017-07-10  7:47 ` [RESEND PATCH v5 00/16] " Javier Martinez Canillas
2017-07-31 15:30 ` Wolfram Sang [this message]
2017-07-31 16:17   ` Javier Martinez Canillas
     [not found]     ` <CABxcv=mdbE0QGjoi3aLzxRqM3-MbkQ_Ai6fShcGVUGSNNqqrqw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=20170731153009.xkjknygpmckv2pfp@ninjato \
    --to=wsa@the-dreams.de \
    --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=javier@dowhile0.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=manabian@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=michal.simek@xilinx.com \
    --cc=nsekhar@ti.com \
    --cc=oss@buserror.net \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=soren.brinkmann@xilinx.com \
    --cc=will.deacon@arm.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