From: Guenter Roeck <linux@roeck-us.net>
To: Rob Herring <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] scripts/dtc: Update to upstream version v1.6.0-51-g183df9e9c2b9
Date: Thu, 11 Feb 2021 19:31:20 -0800 [thread overview]
Message-ID: <20210212033120.GA100407@roeck-us.net> (raw)
Hi Rob,
On Wed, Feb 03, 2021 at 03:26:03PM -0600, Rob Herring wrote:
> This adds the following commits from upstream:
>
> 183df9e9c2b9 gitignore: Ignore the swp files
> 0db6d09584e1 gitignore: Add cscope files
> 307afa1a7be8 Update Jon Loeliger's email
> ca16a723fa9d fdtdump: Fix gcc11 warning
> 64990a272e8f srcpos: increase MAX_SRCFILE_DEPTH
> 163f0469bf2e dtc: Allow overlays to have .dtbo extension
> 3b01518e688d Set last_comp_version correctly in new dtb and fix potential version issues in fdt_open_into
> f7e5737f26aa tests: Fix overlay_overlay_nosugar test case
> 7cd5d5fe43d5 libfdt: Tweak description of assume-aligned load helpers
> a7c404099349 libfdt: Internally perform potentially unaligned loads
> bab85e48a6f4 meson: increase default timeout for tests
> f8b46098824d meson: do not assume python is installed, skip tests
> 30a56bce4f0b meson: fix -Wall warning
> 5e735860c478 libfdt: Check for 8-byte address alignment in fdt_ro_probe_()
> 67849a327927 build-sys: add meson build
> 05874d08212d pylibfdt: allow build out of tree
> 3bc3a6b9fe0c dtc: Fix signedness comparisons warnings: Wrap (-1)
> e1147b159e92 dtc: Fix signedness comparisons warnings: change types
> 04cf1fdc0fcf convert-dtsv0: Fix signedness comparisons warning
> b30013edb878 libfdt: Fix kernel-doc comments
>
> Signed-off-by: Rob Herring <robh@kernel.org>
This patch causes my little-endian microblaze qemu emulations to fail
silently (no console output) in next-20210211. Reverting this patch
together with "scripts: dtc: Build fdtoverlay tool" fixes the problem.
Big endian microblaze emulations are not affected. I can't say if other
emulations are affected because I see too many boot failures in -next
to be able to track down all individual problems.
Guenter
---
Bisect log:
# bad: [671176b0016c80b3943cb5387312c886aba3308d] Add linux-next specific files for 20210211
# good: [92bf22614b21a2706f4993b278017e437f7785b3] Linux 5.11-rc7
git bisect start 'HEAD' 'v5.11-rc7'
# good: [d69fe59127a072f06e51bf101b82413056859ddc] Merge remote-tracking branch 'crypto/master'
git bisect good d69fe59127a072f06e51bf101b82413056859ddc
# bad: [9cbf23a8700e40ce348e5dc83c95add50c8689d3] Merge remote-tracking branch 'spi/for-next'
git bisect bad 9cbf23a8700e40ce348e5dc83c95add50c8689d3
# good: [635a8e981a1f34802668307e0b7bb8834d850a66] Merge remote-tracking branch 'drm-misc/for-linux-next'
git bisect good 635a8e981a1f34802668307e0b7bb8834d850a66
# good: [dbb24458a99eed64fdcc88630e8ac38376720f96] Merge remote-tracking branch 'block/for-next'
git bisect good dbb24458a99eed64fdcc88630e8ac38376720f96
# good: [f82648f1c7dd4709ff34cae8a98978fbf8e47d33] Merge remote-tracking branch 'integrity/next-integrity'
git bisect good f82648f1c7dd4709ff34cae8a98978fbf8e47d33
# good: [b18e8865643e421fc3537d7eb446f1eb9edfdf1b] Merge remote-tracking branch 'iommu/next'
git bisect good b18e8865643e421fc3537d7eb446f1eb9edfdf1b
# good: [6589daf8bb98c75ad1065edad87c099ffb9f5d87] dt-bindings: spi: sunxi: Add H616 compatible string
git bisect good 6589daf8bb98c75ad1065edad87c099ffb9f5d87
# bad: [322322d15b9b912bc8710c367a95a7de62220a72] dt-bindings: ethernet-controller: fix fixed-link specification
git bisect bad 322322d15b9b912bc8710c367a95a7de62220a72
# good: [6e09d75513d2670b7ab91ab3584fc5bcf2675a75] hwmon: (lm70) Use device_get_match_data()
git bisect good 6e09d75513d2670b7ab91ab3584fc5bcf2675a75
# good: [9183908e70e913d2db052588172968da55d82af5] dt-bindings: Fix errors in 'if' schemas
git bisect good 9183908e70e913d2db052588172968da55d82af5
# bad: [59b48a715107d5719b75250059864fa775837425] scripts: dtc: Remove the unused fdtdump.c file
git bisect bad 59b48a715107d5719b75250059864fa775837425
# bad: [79edff12060fe7772af08607eff50c0e2486c5ba] scripts/dtc: Update to upstream version v1.6.0-51-g183df9e9c2b9
git bisect bad 79edff12060fe7772af08607eff50c0e2486c5ba
# good: [b775f49fbc8b07b0c3a4079e6f09f192eaf6e92f] scripts: dtc: Fetch fdtoverlay.c from external DTC project
git bisect good b775f49fbc8b07b0c3a4079e6f09f192eaf6e92f
# first bad commit: [79edff12060fe7772af08607eff50c0e2486c5ba] scripts/dtc: Update to upstream version v1.6.0-51-g183df9e9c2b9
next reply other threads:[~2021-02-12 3:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 3:31 Guenter Roeck [this message]
2021-02-12 14:16 ` [PATCH] scripts/dtc: Update to upstream version v1.6.0-51-g183df9e9c2b9 Rob Herring
2021-02-12 15:17 ` Guenter Roeck
2021-02-12 21:01 ` Rob Herring
2021-02-12 21:51 ` Guenter Roeck
2021-02-12 22:34 ` Rob Herring
2021-02-12 22:50 ` Guenter Roeck
2021-02-15 15:23 ` Michal Simek
2021-02-15 16:15 ` Guenter Roeck
2021-02-12 22:44 ` Guenter Roeck
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=20210212033120.GA100407@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.