From: javier@dowhile0.org (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v5 11/16] arm64: zynqmp: Add generic compatible string for I2C EEPROM
Date: Mon, 21 Aug 2017 13:27:53 +0200 [thread overview]
Message-ID: <CABxcv=mOtPDU4RStdrF1EFci65N8sMB1MG4oKZiTXqUTe7GWHA@mail.gmail.com> (raw)
In-Reply-To: <e64ce8be-599a-5fc5-3194-92aac574173c@xilinx.com>
[snip]
>>
>> diff --git a/arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts b/arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts
>> index ef1b9e573af0..53907b7a7fd9 100644
>> --- a/arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts
>> +++ b/arch/arm64/boot/dts/xilinx/zynqmp-ep108.dts
>> @@ -55,7 +55,7 @@
>> status = "okay";
>> clock-frequency = <400000>;
>> eeprom at 54 {
>> - compatible = "at,24c64";
>> + compatible = "atmel,24c64";
>> reg = <0x54>;
>> };
>> };
>> @@ -64,7 +64,7 @@
>> status = "okay";
>> clock-frequency = <400000>;
>> eeprom at 55 {
>> - compatible = "at,24c64";
>> + compatible = "atmel,24c64";
>> reg = <0x55>;
>> };
>> };
>>
>
> Acked-by: Michal Simek <michal.simek@xilinx.com>
>
Any reasons why this patch was never picked? It was acked two months ago.
Best regards,
Javier
next prev parent reply other threads:[~2017-08-21 11:27 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 [this message]
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
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=mOtPDU4RStdrF1EFci65N8sMB1MG4oKZiTXqUTe7GWHA@mail.gmail.com' \
--to=javier@dowhile0.org \
--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;
as well as URLs for NNTP newsgroup(s).