From: Tom Rini <trini@konsulko.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Adam Ford <aford173@gmail.com>,
U-Boot-Denx <u-boot@lists.denx.de>,
Frieder Schrempf <frieder.schrempf@kontron.de>
Subject: Re: [PATCH 1/2] imx8mm-kontron-n801x-s-u-boot.dtsi: Update for common imx8mm-u-boot.dtsi
Date: Fri, 7 Jan 2022 17:37:18 -0500 [thread overview]
Message-ID: <20220107223718.GJ2773246@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5AZwtwyVKYOQ+saJ-u8mcsWVLQsE6aGAmTAvnppRenH=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On Fri, Jan 07, 2022 at 06:23:25PM -0300, Fabio Estevam wrote:
> On Fri, Jan 7, 2022 at 6:21 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > Now that we have the common binman section information included in
> > mx8mm-u-boot.dtsi we must exclude them from the board dts files. Update
> > this to remove the now duplicate information.
> >
> > Cc: Frieder Schrempf <frieder.schrempf@kontron.de>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > This is based on having all of
> > https://patchwork.ozlabs.org/bundle/trini/2022-01-07-imx8-and-binman-updates/
> > applied which includes
> > https://patchwork.ozlabs.org/project/uboot/list/?series=268510 and so
> > has the common imx8mm-u-boot.dtsi file in question.
>
> Adam has just submitted these two fixes.
Ah good, I'll grab his versions.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-01-07 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 21:21 [PATCH 1/2] imx8mm-kontron-n801x-s-u-boot.dtsi: Update for common imx8mm-u-boot.dtsi Tom Rini
2022-01-07 21:21 ` [PATCH 2/2] phycore-imx8mm-u-boot.dtsi: " Tom Rini
2022-01-07 21:23 ` [PATCH 1/2] imx8mm-kontron-n801x-s-u-boot.dtsi: " Fabio Estevam
2022-01-07 22:37 ` Tom Rini [this message]
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=20220107223718.GJ2773246@bill-the-cat \
--to=trini@konsulko.com \
--cc=aford173@gmail.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--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