From: <Conor.Dooley@microchip.com>
To: <sfr@canb.auug.org.au>, <linux-next@vger.kernel.org>, <hch@lst.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>
Subject: Re: linux-next: Tree for May 3
Date: Wed, 4 May 2022 08:32:19 +0000 [thread overview]
Message-ID: <3f94c9a8-c927-5cc0-7d67-4b21c3d9dbaf@microchip.com> (raw)
In-Reply-To: <20220503172926.08215c77@canb.auug.org.au>
On 03/05/2022 08:29, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20220502:
>
> The input tree still had its build failure so I used the version from
> next-20220426.
>
> The usb tree still had its build failure for which I reverted a commit.
>
> The bitmap tree lost its build failure.
>
> The mm tree still had its build failures for which I applied a supplied
> patch and gained a conflict against the folio tree.
>
> Non-merge commits (relative to Linus' tree): 7492
> 8226 files changed, 410422 insertions(+), 168696 deletions(-)
Hey all,
Not done this before so apologies if I am not reporting this correctly.
The tree for May 3rd does not boot on my PolarFire SoC Icicle kit,
which I have attempted to bisect. The culprit seems to be commit
6424e31b1c05 ("swiotlb: remove swiotlb_init_with_tbl and
swiotlb_init_late_with_tbl")
Please lmk if you need any further information,
Conor.
config: arch/riscv/configs/defconfig
log:
git bisect start
# bad: [44a2f39e611ac0bc1f17c288a583d7f2e5684aa7] Add linux-next specific files for 20220503
git bisect bad 44a2f39e611ac0bc1f17c288a583d7f2e5684aa7
# good: [672c0c5173427e6b3e2a9bbb7be51ceeec78093a] Linux 5.18-rc5
git bisect good 672c0c5173427e6b3e2a9bbb7be51ceeec78093a
# bad: [80a7d9b5288b4c5ad900c7716d851e5d285f6d80] Merge branch 'drm-next' of git://git.freedesktop.org/git/drm/drm.git
git bisect bad 80a7d9b5288b4c5ad900c7716d851e5d285f6d80
# bad: [7c344e7d5be6b8bc9d753294878468cbba96af97] Merge branch 'master' of git://linuxtv.org/mchehab/media-next.git
git bisect bad 7c344e7d5be6b8bc9d753294878468cbba96af97
# bad: [7534d13c1fc508697ea76dc1c403151465ba50ff] Merge branch 'reset/next' of https://git.pengutronix.de/git/pza/linux
git bisect bad 7534d13c1fc508697ea76dc1c403151465ba50ff
# bad: [bfad554357b0b99ca95fbc79016c3fd9559c7205] Merge branch 'for-next' of https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux-mem-ctrl.git
git bisect bad bfad554357b0b99ca95fbc79016c3fd9559c7205
# bad: [5075bc6921b420b16162bfeef073f75f7c43b038] Merge branch 'for-next' of git://git.armlinux.org.uk/~rmk/linux-arm.git
git bisect bad 5075bc6921b420b16162bfeef073f75f7c43b038
# good: [cf46297bbd341132c42e2a47e3e05b2c261c99d1] Merge branch 'fixes' of git://linuxtv.org/mchehab/media-next.git
git bisect good cf46297bbd341132c42e2a47e3e05b2c261c99d1
# good: [c23552d1a15a89db37d4fa95aa8d0a30ad3c4482] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
git bisect good c23552d1a15a89db37d4fa95aa8d0a30ad3c4482
# good: [d7e3c397087fffde68389e7530093dbc2b70c48a] perf stat: Support hybrid --topdown option
git bisect good d7e3c397087fffde68389e7530093dbc2b70c48a
# bad: [3cb4503a330159dc5cf2f8382181ccbabbbaa5b2] x86: remove cruft from <asm/dma-mapping.h>
git bisect bad 3cb4503a330159dc5cf2f8382181ccbabbbaa5b2
# good: [78013eaadf696d2105982abb4018fbae394ca08f] x86: remove the IOMMU table infrastructure
git bisect good 78013eaadf696d2105982abb4018fbae394ca08f
# good: [742519538e6b07250c8085bbff4bd358bc03bf16] swiotlb: pass a gfp_mask argument to swiotlb_init_late
git bisect good 742519538e6b07250c8085bbff4bd358bc03bf16
# good: [3f70356edf5611c28a68d8d5a9c2b442c9eb81e6] swiotlb: merge swiotlb-xen initialization into swiotlb
git bisect good 3f70356edf5611c28a68d8d5a9c2b442c9eb81e6
# bad: [6424e31b1c050a25aea033206d5f626f3523448c] swiotlb: remove swiotlb_init_with_tbl and swiotlb_init_late_with_tbl
git bisect bad 6424e31b1c050a25aea033206d5f626f3523448c
# first bad commit: [6424e31b1c050a25aea033206d5f626f3523448c] swiotlb: remove swiotlb_init_with_tbl and swiotlb_init_late_with_tbl
next prev parent reply other threads:[~2022-05-04 8:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 7:29 linux-next: Tree for May 3 Stephen Rothwell
2022-05-04 8:32 ` Conor.Dooley [this message]
2022-05-09 13:33 ` Conor.Dooley
2022-05-09 14:11 ` Christoph Hellwig
2022-05-09 14:39 ` Conor.Dooley
2022-05-10 11:20 ` Conor.Dooley
2022-05-11 6:22 ` Christoph Hellwig
2022-05-11 6:44 ` Conor.Dooley
2022-05-11 6:48 ` Christoph Hellwig
2022-05-11 10:10 ` Conor.Dooley
2022-05-11 12:37 ` Christoph Hellwig
2022-05-11 14:08 ` Mike Rapoport
2022-05-11 14:10 ` Christoph Hellwig
2022-05-11 14:37 ` Mike Rapoport
2022-05-11 14:40 ` Christoph Hellwig
2022-05-13 7:55 ` Conor.Dooley
2022-05-14 12:18 ` Geert Uytterhoeven
2022-05-16 9:47 ` Conor.Dooley
-- strict thread matches above, loose matches on Subject: below --
2021-05-03 2:59 Stephen Rothwell
2019-05-03 10:00 Stephen Rothwell
2018-05-03 5:13 Stephen Rothwell
2017-05-03 5:54 Stephen Rothwell
2016-05-03 9:37 Stephen Rothwell
2013-05-03 4:10 Stephen Rothwell
2012-05-03 6:38 Stephen Rothwell
2011-05-03 5:47 Stephen Rothwell
2010-05-03 5:16 Stephen Rothwell
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=3f94c9a8-c927-5cc0-7d67-4b21c3d9dbaf@microchip.com \
--to=conor.dooley@microchip.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).