From: "Rafał Miłecki" <zajec5@gmail.com>
To: u-boot@lists.denx.de
Cc: "Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH V2 0/2] fw_env: two minor code cleanups
Date: Wed, 12 Jan 2022 12:39:28 +0100 [thread overview]
Message-ID: <20220112113930.7660-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
Hi,
I'm a long time OpenWrt developer and just recently I started working
with some devices using U-Boot.
I was trying to understand how environment variables are read in user
space and I had some problems understanding fw_env_open() logic. I
eventually got it but I thought I may help further developers by
simpliifying its code a bit.
I hope you may find those patches useful and review / apply them.
Rafał Miłecki (2):
fw_env: make flash_io() take buffer as an argument
fw_env: simplify logic & code paths in the fw_env_open()
tools/env/fw_env.c | 105 +++++++++++++++++++--------------------------
1 file changed, 45 insertions(+), 60 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-12 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:39 Rafał Miłecki [this message]
2022-01-12 11:39 ` [PATCH V2 1/2] fw_env: make flash_io() take buffer as an argument Rafał Miłecki
2022-01-12 11:39 ` [PATCH V2 2/2] fw_env: simplify logic & code paths in the fw_env_open() Rafał Miłecki
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=20220112113930.7660-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=rafal@milecki.pl \
--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