From: Baruch Siach <baruch@tkos.co.il>
To: u-boot@lists.denx.de
Subject: [PATCH 0/4] Updates for ClearFog EEPROM
Date: Mon, 20 Jan 2020 14:25:25 +0200 [thread overview]
Message-ID: <871rru71sa.fsf@tarshish> (raw)
In-Reply-To: <9061c3b635b978a450801a2a5c88b534@lixil.net>
Hi Joel,
On Sun, Jan 19 2020, Joel Johnson wrote:
> On 2020-01-19 01:41, Baruch Siach wrote:
>> On Sun, Jan 19 2020, Joel Johnson wrote:
>>> On 2020-01-19 00:22, Baruch Siach wrote:
>>>> On Sun, Jan 19 2020, Joel Johnson wrote:
>>>>> This set of patches applies on top of
>>>>> https://patchwork.ozlabs.org/cover/1200324/,
>>>>> based on testing using the static configuration fallback updates in a
>>>>> related patch series.
>>>>
>>>> Thank you very much.
>>>>
>>>> I'm currently working on an updated series with some significant
>>>> changes. These include rename of sys_eeprom to tlv_eeprom; move of TLV
>>>> parse code to board/solidrun/common/; and support for TLV read in
>>>> pre-relocation phase. I'll add your fixes where applicable.
>>>>
>>>> I hope to post v2 in the coming week.
>>>>
>>>> baruch
>>>
>>> Sounds good, thanks! I'm also getting ready to shoot out a V2 of my static
>>> ClearFog Base support which based on prior review I've rebased on your
>>> run-time config series. If it works for you, I'll go ahead and still send
>>> that
>>> out for review, modulo your further changes. Are you expecting the
>>> TLV/EEPROM
>>> change updates to be included in time for the current merge window?
>>
>> I hope to have TLV EEPROM ready for v2020.04.
>
> Hmm, I was hoping to have the static config for ClearFog Base merged in the
> current merge window, so just to be clear is that what you're targeting by
> v2020.04 as well?
Yes. Code merged in this merge windows will appear in the next release
which is v2020.04.
I have just posted the updated series with your fixes squashed in,
sometimes in a different form (like the non CMD_TLV_EEPROM build fix).
> With my recent rebasing, I believe I made the changes compatible between
> static and runtime configuration, but it's less important what order they're
> applied in - i.e. I can rebase again back on master and retain the
> alignment. Perhaps it would be possible to merge the static changes and then
> update the static config entries' help text with a subsequent merge of your
> runtime work?
I'm not sure what you mean hear.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2020-01-20 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 7:10 [PATCH 0/4] Updates for ClearFog EEPROM Joel Johnson
2020-01-19 7:10 ` [PATCH 1/4] cmd: sys_eeprom: add missing implicit header Joel Johnson
2020-01-19 7:10 ` [PATCH 2/4] cmd: sys_eeprom reflect I2C dependency in Kconfig Joel Johnson
2020-01-19 7:10 ` [PATCH 3/4] arm: mvebu: clearfog: don't set SPL misc Joel Johnson
2020-01-19 7:10 ` [PATCH 4/4] arm: mvebu: clearfog: fix compile w/o EEPROM Joel Johnson
2020-01-19 7:22 ` [PATCH 0/4] Updates for ClearFog EEPROM Baruch Siach
2020-01-19 7:29 ` Joel Johnson
2020-01-19 8:41 ` Baruch Siach
2020-01-19 16:10 ` Joel Johnson
2020-01-20 12:25 ` Baruch Siach [this message]
2020-01-20 17:01 ` Joel Johnson
2020-04-15 9:49 ` Stefan Roese
2020-04-16 12:22 ` Baruch Siach
2020-04-16 12:38 ` Stefan Roese
2020-04-16 14:36 ` Joel Johnson
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=871rru71sa.fsf@tarshish \
--to=baruch@tkos.co.il \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.