From: Ingo Molnar <mingo@kernel.org>
To: "Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>
Cc: "ben@decadent.org.uk" <ben@decadent.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 01/15] liblockdep: Fix undefined symbol prandom_u32
Date: Fri, 26 May 2017 08:54:44 +0200 [thread overview]
Message-ID: <20170526065444.neuxegeowzvlle5c@gmail.com> (raw)
In-Reply-To: <20170525123601.yhgnlujb4c4mvcfw@sasha-lappy>
* Levin, Alexander (Sasha Levin) <alexander.levin@verizon.com> wrote:
> On Wed, May 24, 2017 at 09:53:37AM +0200, Ingo Molnar wrote:
> >
> > So I'm not sure how you sent these patches, but probably due to the lack of a
> > boilerplate message, the order was all mixed up. I got the patch order right on
> > the third attempt.
> >
> > But then I encountered this build failure (when applied to Linus's latest tree):
> >
> > triton:~/tip/tools/lib/lockdep> make
> > CC common.o
> > CC lockdep.o
> > In file included from lockdep.c:25:0:
> > ../../../kernel/locking/lockdep.c:33:28: fatal error: linux/sched/mm.h: No such
> > file or directory
> > #include <linux/sched/mm.h>
> > ^
>
> Heh, apparently a bunch of stuff changed between the point when I sent my
> original pull request and now... I'll resend with additional fixes.
Yeah, and also note that this is v4.13 material at best - liblockdep broke a long
time ago so it falls under 'development', not 'regression fixes'.
Thanks,
Ingo
prev parent reply other threads:[~2017-05-26 6:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 0:01 alexander.levin
2017-05-18 0:01 ` [PATCH 02/15] liblockdep: Reduce MAX_LOCK_DEPTH to avoid overflowing lock_chain::depth alexander.levin
2017-05-18 0:01 ` [PATCH 04/15] liblockdep: Enable -Wall by default alexander.levin
2017-05-18 0:01 ` [PATCH 03/15] liblockdep: Define the ARRAY_SIZE() macro alexander.levin
2017-05-18 0:01 ` [PATCH 05/15] liblockdep: Fix 'unused value' warnings alexander.levin
2017-05-18 0:01 ` [PATCH 06/15] liblockdep: Fix 'set but not used' warnings alexander.levin
2017-05-18 0:01 ` [PATCH 07/15] liblockdep: Fix 'defined but not used' warning for init_utsname() alexander.levin
2017-05-18 0:01 ` [PATCH 09/15] MAINTAINERS: update email for Sasha Levin alexander.levin
2017-05-18 0:01 ` [PATCH 10/15] tools: add install make target for liblockdep alexander.levin
2017-05-18 0:01 ` [PATCH 08/15] liblockdep: Remove -lpthread compiler option alexander.levin
2017-05-18 0:01 ` [PATCH 12/15] tools: liblockdep: fix compilation for 4.11 alexander.levin
2017-05-18 0:01 ` [PATCH 11/15] tools: liblockdep: Don't mix fd-based and stream IO alexander.levin
2017-05-18 0:01 ` [PATCH 15/15] tools: liblockdep: Use LDFLAGS alexander.levin
2017-05-18 0:01 ` [PATCH 13/15] tools: liblockdep: Fix object file paths used in an out-of-tree build alexander.levin
2017-05-18 0:01 ` [PATCH 14/15] tools: liblockdep: Remove double-quotes from soname alexander.levin
2017-05-24 7:53 ` [PATCH 01/15] liblockdep: Fix undefined symbol prandom_u32 Ingo Molnar
2017-05-25 12:34 ` Levin, Alexander (Sasha Levin)
2017-05-26 6:54 ` Ingo Molnar [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=20170526065444.neuxegeowzvlle5c@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=alexander.levin@verizon.com \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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
all inboxes | Powered by JetHome®