From: Tom Rini <trini@konsulko.com>
To: Patrick Delaunay <patrick.delaunay@foss.st.com>
Cc: u-boot@lists.denx.de, Marek Vasut <marex@denx.de>,
Simon Glass <sjg@chromium.org>,
U-Boot STM32 <uboot-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v1 1/5] cmd: Fix up warnings in flash.c
Date: Fri, 21 Jan 2022 14:02:58 -0500 [thread overview]
Message-ID: <20220121190258.GH7004@bill-the-cat> (raw)
In-Reply-To: <20220104142328.v1.1.Iaa7c4564c1e7d57e198f7621d124cddaa3296c4a@changeid>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
On Tue, Jan 04, 2022 at 02:23:57PM +0100, Patrick Delaunay wrote:
> Tidy up the warnings reported by checkpatch.pl to prepare next patches
>
> Signed-off-by: Patrick Delaunay <patrick.delaunay@foss.st.com>
> Reviewed-by: Simon Glass <sjg@chromium.org>
> Reviewed-by: Stefan Roese <sr@denx.de>
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-21 19:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 13:23 [PATCH v1 0/5] configs: Migrate CONFIG_SYS_MAX_FLASH_BANKS to Kconfig Patrick Delaunay
2022-01-04 13:23 ` [PATCH v1 1/5] cmd: Fix up warnings in flash.c Patrick Delaunay
2022-01-05 8:42 ` Stefan Roese
2022-01-21 19:02 ` Tom Rini [this message]
2022-01-04 13:23 ` [PATCH v1 2/5] mtd: cfi: introduce CFI_FLASH_BANKS Patrick Delaunay
2022-01-05 8:43 ` Stefan Roese
2022-01-21 19:03 ` Tom Rini
2022-01-04 13:23 ` [PATCH v1 3/5] mtd: cfi: change CONFIG_SYS_MAX_FLASH_BANKS_DETECT as boolean Patrick Delaunay
2022-01-05 8:43 ` Stefan Roese
2022-01-21 19:03 ` Tom Rini
2022-01-04 13:24 ` [PATCH v1 4/5] configs: Migrate CONFIG_SYS_MAX_FLASH_BANKS to Kconfig Patrick Delaunay
2022-01-05 8:43 ` Stefan Roese
2022-01-21 19:03 ` Tom Rini
2022-01-04 13:24 ` [PATCH v1 5/5] Convert CONFIG_AT91_EFLASH " Patrick Delaunay
2022-01-05 8:44 ` Stefan Roese
2022-01-05 8:53 ` Eugen.Hristev
2022-01-21 19:03 ` 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=20220121190258.GH7004@bill-the-cat \
--to=trini@konsulko.com \
--cc=marex@denx.de \
--cc=patrick.delaunay@foss.st.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=uboot-stm32@st-md-mailman.stormreply.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox