public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 2/2] build/DTC: fix sed usage in DTC command
Date: Thu, 25 Feb 2021 08:25:53 -0500	[thread overview]
Message-ID: <20210225132553.GC10169@bill-the-cat> (raw)
In-Reply-To: <20210213100632.6249-3-royger@FreeBSD.org>

On Sat, Feb 13, 2021 at 11:06:32AM +0100, Roger Pau Monne wrote:

> Current sed usage in the DTC command relies on GNU sed specific -i
> option which has a slightly different syntax for BSD sed and always
> expects an extension to be provided in order to create a backup file.
> 
> Instead drop the cat concatenation done before the sed call and use
> sed itself to edit and concatenate the files.
> 
> No functional change intended.
> 
> Signed-off-by: Roger Pau Monn? <royger@FreeBSD.org>

Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210225/e1460cde/attachment.sig>

      parent reply	other threads:[~2021-02-25 13:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-13 10:06 [PATCH 0/2] Fixes for BSD sed compatibility Roger Pau Monne
2021-02-13 10:06 ` [PATCH 1/2] scripts/check-config.sh: fix to be compatible with BSD sed Roger Pau Monne
2021-02-13 16:42   ` Warner Losh
2021-02-18  4:45   ` Simon Glass
2021-02-25 13:25   ` Tom Rini
2021-02-13 10:06 ` [PATCH 2/2] build/DTC: fix sed usage in DTC command Roger Pau Monne
2021-02-13 16:43   ` Warner Losh
2021-02-22  9:17   ` Roger Pau Monné
2021-02-25 13:25   ` 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=20210225132553.GC10169@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