From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/6] scripts/dtc: rework dtc import handling
Date: Wed, 25 Sep 2019 11:51:27 +0200 [thread overview]
Message-ID: <20190925095127.tekk37oaqmvdfyxj@pengutronix.de> (raw)
In-Reply-To: <20190923121018.31574-1-a.fatoum@pengutronix.de>
On Mon, Sep 23, 2019 at 02:10:12PM +0200, Ahmad Fatoum wrote:
> Linux upstream doesn't use fdtget. barebox does however for IMD.
> Commits 46bdae84e8 ("dtc: Update update-dtc-source.sh from Linux") and
> 4e731e48d4 ("scripts/dtc: Update to upstream version v1.5.0") broke
> this, which the first two patches in this series fix. They should be
> applied to upstream/master.
>
> This probably went undtected because an old ftdget would survive a
> mrproper, so this issue only happens on fresh check-outs.
>
> The other 4 patches address the fact that the process by which we update
> dtc is error-prone. This is evident by this patch and 1df07fbcdf
> ("scripts/dtc: Reenable fdtget"), which fixed the same issue a year
> prior.
>
> To address this add documentation on how to update dtc and make the
> script easier to use. The update to v1.5.1 is included as well to test
> this out, but can be dropped.
>
> Ahmad Fatoum (6):
> scripts/dtc: Reinstate barebox-specifics in update-dtc-source.sh
> scripts/dtc: reinstate building of fdtget along with dtc
> scripts/dtc: git rm old files as part of update process
> scripts/dtc: mention dtc project in update-dtc-source.sh commit
> message
> scripts/dtc: Update to upstream version v1.5.1
> Documentation: document barebox device tree handling
Applied, thanks
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-09-25 9:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 12:10 Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 1/6] scripts/dtc: Reinstate barebox-specifics in update-dtc-source.sh Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 2/6] scripts/dtc: reinstate building of fdtget along with dtc Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 3/6] scripts/dtc: git rm old files as part of update process Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 4/6] scripts/dtc: mention dtc project in update-dtc-source.sh commit message Ahmad Fatoum
2019-09-23 13:49 ` Roland Hieber
2019-09-23 12:10 ` [PATCH 5/6] scripts/dtc: Update to upstream version v1.5.1 Ahmad Fatoum
2019-09-23 12:10 ` [PATCH 6/6] Documentation: document barebox device tree handling Ahmad Fatoum
2019-09-25 9:51 ` Sascha Hauer [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=20190925095127.tekk37oaqmvdfyxj@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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