From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH] v7a: barebox: update v2021.11.0 → v2022.01.0
Date: Tue, 18 Jan 2022 15:32:20 +0100 [thread overview]
Message-ID: <aad0436b-6ca0-749b-4384-80e6ee4d0a50@pengutronix.de> (raw)
In-Reply-To: <Yeag5Ky4frHZg2Gl@pengutronix.de>
Hello Robert,
On 18.01.22 12:13, Robert Schwebel wrote:
> Hi Ahmad,
>
> On Tue, Jan 18, 2022 at 11:56:36AM +0100, Ahmad Fatoum wrote:
>> Freshest barebox release incorporates the OMAP patches we have in the
>> BSP. Bump up the release and drop these two patches in return.
>>
>> The release also introduced CONFIG_STM32_BSEC_WRITE, which enables
>> blowing e-fuses on STM32MP1 SoCs, e.g. to persist an Ethernet address.
>> We support a couple of STM32MP1 boards, so it makes sense to enable
>> this option. All other Kconfig changes are those of olddefconfig.
>
> Could you rebase against master? I forgot to merge next into master
> recently, so there were some patches.
I fetched and my master HEAD commit is
5e3d0b4ebd31 ("doc: document patch download with b4 from lore.distrokit.org")
And this patch cleanly applies there:
b4 am -o- '<Yeag5Ky4frHZg2Gl@pengutronix.de>' | git am
Should I rebase onto something else?
Cheers,
Ahmad
>
> rsc
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2022-01-18 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 10:56 Ahmad Fatoum
2022-01-18 11:13 ` Robert Schwebel
2022-01-18 14:32 ` Ahmad Fatoum [this message]
2022-01-22 10:52 ` Robert Schwebel
2022-01-22 15:19 ` Robert Schwebel
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=aad0436b-6ca0-749b-4384-80e6ee4d0a50@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=r.schwebel@pengutronix.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