Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [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>


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170731/696b547b/attachment-0001.sig>

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

Thread overview: 35+ 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 03/16] ARM: dts: efm32: Add generic compatible string for I2C EEPROM Javier Martinez Canillas
2017-08-16 14:21   ` Javier Martinez Canillas
2017-06-15 18:54 ` [RESEND PATCH v5 04/16] ARM: dts: keystone: " Javier Martinez Canillas
2017-06-15 18:54 ` [RESEND PATCH v5 05/16] ARM: dts: lpc18xx: " Javier Martinez Canillas
2017-06-15 18:54 ` [RESEND PATCH v5 06/16] ARM: dts: r7s72100: " Javier Martinez Canillas
2017-06-16 13:36   ` Simon Horman
2017-06-15 18:54 ` [RESEND PATCH v5 07/16] ARM: dts: koelsch: " Javier Martinez Canillas
2017-06-16 13:36   ` Simon Horman
2017-06-15 18:54 ` [RESEND PATCH v5 08/16] ARM: dts: socfpga: " Javier Martinez Canillas
2017-11-07  8:20   ` Javier Martinez Canillas
2017-06-15 18:54 ` [RESEND PATCH v5 09/16] ARM: dts: uniphier: " Javier Martinez Canillas
2017-06-15 18:54 ` [RESEND PATCH v5 10/16] ARM: dts: zynq: " Javier Martinez Canillas
2017-06-21 11:43   ` Michal Simek
2017-08-23 14:28     ` Javier Martinez Canillas
2017-08-24 13:44       ` Michal Simek
2017-09-21  9:41         ` Javier Martinez Canillas
2017-09-25  8:06           ` Michal Simek
2017-09-26  8:00             ` Javier Martinez Canillas
2017-06-15 18:54 ` [RESEND PATCH v5 11/16] arm64: zynqmp: " Javier Martinez Canillas
2017-06-21 11:43   ` Michal Simek
2017-08-21 11:27     ` Javier Martinez Canillas
2017-08-21 12:04       ` Michal Simek
2017-08-21 12:58         ` Javier Martinez Canillas
2017-07-10  7:47 ` [RESEND PATCH v5 00/16] eeprom: at24: Add OF device ID table Javier Martinez Canillas
2017-07-31 15:30 ` Wolfram Sang [this message]
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=20170731153009.xkjknygpmckv2pfp@ninjato \
    --to=wsa@the-dreams.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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