* Levin, Alexander (Sasha Levin) 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 th
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
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
From: Ben Hutchings
__lock_pin_lock() now calls prandom_u32() which is not defined in
liblockdep. __lock_pin_lock() and its caller lock_pin_lock() are dead
code in liblockdep, but we still need to provide a definition of
prandom_u32() in case lazy binding is disabled.
Fixes: e7904a28f533 ("lock
4 matches
Mail list logo