From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] host-dtc: remove old patch for version 1.6.0
Date: Fri, 8 Apr 2022 15:36:05 +0200 [thread overview]
Message-ID: <20220408133605.123341-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20220405155701.15497-1-bruno.thomsen@gmail.com>
Thanks, applied as 824e3cb42a32570eec4217ebdad0ed9e6862dc77.
Michael
[sent from post-receive hook]
On Fri, 08 Apr 2022 15:36:05 +0200, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> After version bumping default host-dtc version from 1.6.0 to 1.6.1 there
> was left an old patch for 1.6.0. Removing the patch so we don't collect
> clutter.
>
> Fixes: 89a84394677e ("host-dtc: version bump 1.6.0 to 1.6.1")
>
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20220405155701.15497-1-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/patches/dtc-v1.6.0/0001-fdtdump-Fix-gcc11-warning.patch b/patches/dtc-v1.6.0/0001-fdtdump-Fix-gcc11-warning.patch
> deleted file mode 100644
> index 052419940a15..000000000000
> --- a/patches/dtc-v1.6.0/0001-fdtdump-Fix-gcc11-warning.patch
> +++ /dev/null
> @@ -1,30 +0,0 @@
> -From: David Gibson <david@gibson.dropbear.id.au>
> -Date: Wed, 6 Jan 2021 14:52:26 +1100
> -Subject: [PATCH] fdtdump: Fix gcc11 warning
> -
> -In one place, fdtdump abuses fdt_set_magic(), passing it just a small char
> -array instead of the full fdt header it expects. That's relying on the
> -fact that in fact fdt_set_magic() will only actually access the first 4
> -bytes of the buffer.
> -
> -This trips a new warning in GCC 11 - and it's entirely possible it was
> -always UB. So, don't do that.
> -
> -Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ----
> - fdtdump.c | 2 +-
> - 1 file changed, 1 insertion(+), 1 deletion(-)
> -
> -diff --git a/fdtdump.c b/fdtdump.c
> -index 9613befede71..d9fb374a59be 100644
> ---- a/fdtdump.c
> -+++ b/fdtdump.c
> -@@ -217,7 +217,7 @@ int main(int argc, char *argv[])
> - char *p = buf;
> - char *endp = buf + len;
> -
> -- fdt_set_magic(smagic, FDT_MAGIC);
> -+ fdt32_st(smagic, FDT_MAGIC);
> -
> - /* poor man's memmem */
> - while ((endp - p) >= FDT_MAGIC_SIZE) {
> diff --git a/patches/dtc-v1.6.0/series b/patches/dtc-v1.6.0/series
> deleted file mode 100644
> index a7e9d0319ba0..000000000000
> --- a/patches/dtc-v1.6.0/series
> +++ /dev/null
> @@ -1,4 +0,0 @@
> -# generated by git-ptx-patches
> -#tag:base --start-number 1
> -0001-fdtdump-Fix-gcc11-warning.patch
> -# cb5c26c7ab3ae2082ecff7af4de4e8c5 - git-ptx-patches magic
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
prev parent reply other threads:[~2022-04-08 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 15:57 [ptxdist] [PATCH] " Bruno Thomsen
2022-04-08 13:36 ` Michael Olbrich [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=20220408133605.123341-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bruno.thomsen@gmail.com \
--cc=ptxdist@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