From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] KM/IVM: remove ivm_read_eeprom(void)
Date: Mon, 02 Feb 2015 16:55:47 +0100 [thread overview]
Message-ID: <54CF9E03.2070805@keymile.com> (raw)
In-Reply-To: <54AB9AAA.4050906@keymile.com>
Hello Tom and Holger,
On 01/06/2015 09:19 AM, Brunck, Holger wrote:
> On 01/05/2015 07:47 PM, Tom Rini wrote:
>> On Tue, Dec 23, 2014 at 02:08:57PM +0100, Valentin Longchamp wrote:
>>
>>> This is not used anymore since the procedure was split into a simple
>>> read function and a later alaysis.
>>>
>>> The ivm_read_eeprom name is now used for the previous
>>> ivm_simple_read_eeprom function.
>>>
>>> Signed-off-by: Valentin Longchamp <valentin.longchamp@keymile.com>
>>
>> This doesn't apply (but 1-4 does) because there's no
>> ivm_simple_read_eeprom today. Or have I gone crazy? Thanks!
>>
>
> you are right this is missing. I assume that there is a patch missing in his
> serie. Unfortunately Valentin is not in until the end of january, so I propose
> to skip this patch series for this merge window.
>
Yes the first patch was missing. I have unfortunately not included it in my
first submission just before leaving for holiday. I am sending a V2 that fixes
this right now.
Sorry for the noise
Valentin
prev parent reply other threads:[~2015-02-02 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 13:08 [U-Boot] [PATCH 0/5] keymile: enhance IVM reading Valentin Longchamp
2014-12-23 13:08 ` [U-Boot] [PATCH 1/5] kirkwood/km_arm: read the IVM eeprom earlier Valentin Longchamp
2014-12-23 13:08 ` [U-Boot] [PATCH 2/5] 85xx/kmp204x: " Valentin Longchamp
2014-12-23 13:08 ` [U-Boot] [PATCH 3/5] 83xx/km83xx: " Valentin Longchamp
2014-12-23 13:08 ` [U-Boot] [PATCH 4/5] 82xx/km82xx: " Valentin Longchamp
2014-12-23 13:08 ` [U-Boot] [PATCH 5/5] KM/IVM: remove ivm_read_eeprom(void) Valentin Longchamp
2015-01-05 18:47 ` Tom Rini
2015-01-06 8:19 ` Holger Brunck
2015-02-02 15:55 ` Valentin Longchamp [this message]
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=54CF9E03.2070805@keymile.com \
--to=valentin.longchamp@keymile.com \
--cc=u-boot@lists.denx.de \
/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