From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Trevor Woerner <twoerner@gmail.com>
Subject: Re: [PATCH 4/6] moveconfig: Use a function to write files
Date: Tue, 25 Jan 2022 10:58:09 -0500 [thread overview]
Message-ID: <20220125155809.GX7515@bill-the-cat> (raw)
In-Reply-To: <20211218215435.1159723-5-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
On Sat, Dec 18, 2021 at 02:54:33PM -0700, Simon Glass wrote:
> At present there is quite a bit of ad-hoc code writing to files. The
> treatment of newlines is different in some of them. Put it in a function
> and set the unicode encoding correctly.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-25 15:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 21:54 [PATCH 0/6] moveconfig: Improve the pylist score a little Simon Glass
2021-12-18 21:54 ` [PATCH 1/6] moveconfig: Use single quotes Simon Glass
2021-12-18 22:16 ` Heinrich Schuchardt
2021-12-28 8:33 ` Simon Glass
2022-01-25 15:57 ` Tom Rini
2021-12-18 21:54 ` [PATCH 2/6] moveconfig: Convert to ArgumentParser Simon Glass
2021-12-18 22:32 ` Heinrich Schuchardt
2021-12-18 23:33 ` Simon Glass
2022-01-25 15:57 ` Tom Rini
2021-12-18 21:54 ` [PATCH 3/6] moveconfig: Drop check for old Python Simon Glass
2021-12-18 22:27 ` Heinrich Schuchardt
2022-01-25 15:58 ` Tom Rini
2021-12-18 21:54 ` [PATCH 4/6] moveconfig: Use a function to write files Simon Glass
2022-01-25 15:58 ` Tom Rini [this message]
2021-12-18 21:54 ` [PATCH 5/6] moveconfig: Use a function to read files Simon Glass
2022-01-25 15:58 ` Tom Rini
2021-12-18 21:54 ` [PATCH 6/6] moveconfig: Fix some pylint errors Simon Glass
2022-01-25 15:58 ` Tom Rini
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=20220125155809.GX7515@bill-the-cat \
--to=trini@konsulko.com \
--cc=sjg@chromium.org \
--cc=twoerner@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
--cc=yamada.masahiro@socionext.com \
/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.