All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Joe Hershberger <joe.hershberger@ni.com>,
	Stefan Herbrechtsmeier
	<stefan.herbrechtsmeier-oss@weidmueller.com>
Subject: Re: [PATCH V4 01/14] env: Complete generic support for writable list
Date: Thu, 2 Feb 2023 15:57:55 +0100	[thread overview]
Message-ID: <76940acf-11f6-2300-fadc-8e440f2818dd@denx.de> (raw)
In-Reply-To: <1251f03b-39d0-ad28-444f-4b7666b681ee@siemens.com>

On 2/2/23 14:51, Jan Kiszka wrote:
> On 02.02.23 13:48, Marek Vasut wrote:
>> On 2/2/23 09:07, Jan Kiszka wrote:
>>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>>
>>> This completes what 890feecaab72 started by selecting ENV_APPEND and
>>> loading the default env before any other sources. This ensures that load
>>> operations pick up all non-writable vars from the default env and only
>>> permitted parts from other locations according to the regular
>>> priorities.
>>>
>>> With this change, boards only need to define the list of writable
>>> variables but no longer have to provide a custom env_get_location
>>> implementation.
>>>
>>> CC: Joe Hershberger <joe.hershberger@ni.com>
>>> CC: Marek Vasut <marex@denx.de>
>>> CC: Stefan Herbrechtsmeier <stefan.herbrechtsmeier-oss@weidmueller.com>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>> Reviewed-by: Marek Vasut <marex@denx.de>
>>
>> Maybe just send this one as a separate patch, so it can go in separately
>> from this series.
> 
> In fact, patch 1 and 2 are foundations and could be picked independently
> of rest if preferred. I don't mind waiting for the whole but I can also
> split if it helps the maintainer(s).

I suspect splitting off the u-boot (env) and other core parts from the 
iot2050 into separate series would make it easier to apply to the right 
tree. Just note down the dependencies in the commit message under --- or 
in cover letter, if there are any.

  reply	other threads:[~2023-02-02 14:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02  8:07 [PATCH V4 00/14] IOT2050-related enhancements Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 01/14] env: Complete generic support for writable list Jan Kiszka
2023-02-02 12:48   ` Marek Vasut
2023-02-02 13:51     ` Jan Kiszka
2023-02-02 14:57       ` Marek Vasut [this message]
2023-02-02  8:07 ` [PATCH V4 02/14] env: Couple networking-related variable flags to CONFIG_NET Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 03/14] tools: Add script for converting public key into device tree include Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 04/14] board: siemens: iot2050: Split the build for PG1 and PG2 Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 05/14] arm: dts: iot2050: Use the auto generator nodes for fdt Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 06/14] iot2050: Update firmware layout Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 07/14] iot2050: Add watchdog start to bootcmd Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 08/14] iot2050: Add CONFIG_ENV_FLAGS_LIST_STATIC Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 09/14] arm: dts: iot2050: Allow verifying U-Boot proper by SPL Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 10/14] iot2050: Add script for signing artifacts Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 11/14] arm: dts: iot2050: Optionally embed OTP programming data into image Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 12/14] doc: iot2050: Add a note about the watchdog firmware Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 13/14] board: siemens: iot2050: use the named gpio to control the user-button Jan Kiszka
2023-02-02  8:07 ` [PATCH V4 14/14] iot2050: Refresh defconfigs and activate CONFIG_EFI_SCROLL_ON_CLEAR_SCREEN Jan Kiszka

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=76940acf-11f6-2300-fadc-8e440f2818dd@denx.de \
    --to=marex@denx.de \
    --cc=jan.kiszka@siemens.com \
    --cc=joe.hershberger@ni.com \
    --cc=stefan.herbrechtsmeier-oss@weidmueller.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 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.