From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Alexander Aring <aahringo@redhat.com>,
David Teigland <teigland@redhat.com>,
Christine Caulfield <ccaulfie@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
cluster-devel@redhat.com
Subject: dlm build failure (was: Re: linux-next: Tree for Nov 22)
Date: Tue, 22 Nov 2022 11:41:38 +0100 [thread overview]
Message-ID: <CAMuHMdX-vHH5b_Qg6-CyB4kRhHaHN=HW=FeRkJ85EM7jL41Egw@mail.gmail.com> (raw)
In-Reply-To: <20221122183833.6509537e@canb.auug.org.au>
On Tue, Nov 22, 2022 at 8:40 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Merging dlm/next (dbb751ffab0b fs: dlm: parallelize lowcomms socket handling)
noreply@ellerman.id.au reported a build failure for e.g. m68k/defconfig[1]:
ERROR: modpost: "lockdep_is_held" [fs/dlm/dlm.ko] undefined!
which I have bisected to this commit. The corresponding patch does not seem
to have been posted for public review to any mailing list archived by lore.
[1] http://kisskb.ellerman.id.au/kisskb/buildresult/14835766/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2022-11-22 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 7:38 linux-next: Tree for Nov 22 Stephen Rothwell
2022-11-22 10:41 ` Geert Uytterhoeven [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='CAMuHMdX-vHH5b_Qg6-CyB4kRhHaHN=HW=FeRkJ85EM7jL41Egw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=aahringo@redhat.com \
--cc=ccaulfie@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=teigland@redhat.com \
/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).