From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] moveconfig: prepare moving CONFIG_SYS_SPI_U_BOOT_OFFS to Kconfig step 3
Date: Mon, 26 Aug 2019 09:38:57 -0400 [thread overview]
Message-ID: <20190826133857.GP26850@bill-the-cat> (raw)
In-Reply-To: <1566481318-16029-4-git-send-email-hannes.schmelzer@br-automation.com>
On Thu, Aug 22, 2019 at 03:41:44PM +0200, Hannes Schmelzer wrote:
> Exact two boards are referencing CONFIG_SYS_SPI_U_BOOT_OFFS to another
> define, we replace this manually with the value for having a clean run
> of moveconfig.py afterwards.
>
> Signed-off-by: Hannes Schmelzer <hannes.schmelzer@br-automation.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190826/49eacbd0/attachment.sig>
next prev parent reply other threads:[~2019-08-26 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 13:41 [U-Boot] [PATCH 0/5] convert CONFIG_SYS_SPI_U_BOOT_OFFS to Kconfig Hannes Schmelzer
2019-08-22 13:41 ` [U-Boot] [PATCH 1/5] moveconfig: prepare moving CONFIG_SYS_SPI_U_BOOT_OFFS to Kconfig step 1 Hannes Schmelzer
2019-08-26 13:38 ` Tom Rini
2019-08-22 13:41 ` [U-Boot] [PATCH 2/5] moveconfig: prepare moving CONFIG_SYS_SPI_U_BOOT_OFFS to Kconfig step 2 Hannes Schmelzer
2019-08-26 13:38 ` Tom Rini
2019-08-22 13:41 ` [U-Boot] [PATCH 3/5] moveconfig: prepare moving CONFIG_SYS_SPI_U_BOOT_OFFS to Kconfig step 3 Hannes Schmelzer
2019-08-26 13:38 ` Tom Rini [this message]
2019-08-22 13:41 ` [U-Boot] [PATCH 4/5] moveconfig: prepare moving CONFIG_SYS_SPI_U_BOOT_OFFS to Kconfig step 4 Hannes Schmelzer
2019-08-22 20:28 ` Chris Packham
2019-08-26 13:39 ` Tom Rini
2019-08-22 13:41 ` [U-Boot] [PATCH 5/5] Convert CONFIG_SYS_SPI_U_BOOT_OFFS to Kconfig Hannes Schmelzer
2019-08-26 13:39 ` 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=20190826133857.GP26850@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox