From: "Marcus Comstedt" <marcus-S4ne242Fi5M@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: Devicetree Compiler
<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: Re: [PATCH] libfdt: Remove superfluous NUL character from overlay symbols
Date: Mon, 25 May 2020 08:53:30 +0200 [thread overview]
Message-ID: <yf97dx0mro5.fsf@mc.pp.se> (raw)
In-Reply-To: <20200525051555.GE23110-K0bRW+63XPQe6aEkudXLsA@public.gmane.org> (david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org's message of "Mon, 25 May 2020 15:15:55 +1000")
Hi David,
David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> writes:
> This patch causes "make check" failures.
Ah. This patch was for U-Boot, and Simon asked me to upstream it, but
I see now that in your repo you already have another fix (d9c55f85)
for the same issue. Then applying my fix makes no sense for you of
course. Sorry about that.
// Marcus
next prev parent reply other threads:[~2020-05-25 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 15:12 [PATCH] libfdt: Remove superfluous NUL character from overlay symbols Marcus Comstedt
[not found] ` <20200523151239.8849-1-marcus-S4ne242Fi5M@public.gmane.org>
2020-05-25 5:15 ` David Gibson
[not found] ` <20200525051555.GE23110-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2020-05-25 6:53 ` Marcus Comstedt [this message]
[not found] <20200522164136.26069-1-marcus@mc.pp.se>
[not found] ` <CAPnjgZ1eU7xOgfGd_6bnUXs_98YOp8gfCz4YHHoHXtCY_h1_Hw@mail.gmail.com>
[not found] ` <yf94ks627a2.fsf@mc.pp.se>
[not found] ` <yf94ks627a2.fsf-S4ne242Fi5M@public.gmane.org>
2020-05-23 14:57 ` Simon Glass
2020-05-23 15:13 ` Marcus Comstedt
[not found] ` <yf9o8qe8z1c.fsf-S4ne242Fi5M@public.gmane.org>
2020-05-25 2:15 ` Simon Glass
[not found] ` <CAPnjgZ2C3HxdZqYAS_g-CEAq1CTVvdEvaz6NiCowpd11d9f5WA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-06-13 3:11 ` sjg-hpIqsD4AKlfQT0dZR+AlfA
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=yf97dx0mro5.fsf@mc.pp.se \
--to=marcus-s4ne242fi5m@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).