On Thu, Aug 07, 2014 at 06:18:34PM -0700, Davidlohr Bueso wrote:
> On Tue, 2014-08-05 at 10:42 -0700, Davidlohr Bueso wrote:
> > On Tue, 2014-08-05 at 15:04 +0200, Geert Uytterhoeven wrote:
> > > It looks like you forgot to update frv? It's been failing on -next since
> > > a
> > > few days:
>
>
On 08/07/2014 06:18 PM, Davidlohr Bueso wrote:
On Tue, 2014-08-05 at 10:42 -0700, Davidlohr Bueso wrote:
On Tue, 2014-08-05 at 15:04 +0200, Geert Uytterhoeven wrote:
It looks like you forgot to update frv? It's been failing on -next since a
few days:
Anyway developers can be alerted sooner a
On Tue, 2014-08-05 at 10:42 -0700, Davidlohr Bueso wrote:
> On Tue, 2014-08-05 at 15:04 +0200, Geert Uytterhoeven wrote:
> > It looks like you forgot to update frv? It's been failing on -next since a
> > few days:
Anyway developers can be alerted sooner about this (ie: while its still
in -next ph
On Tue, 2014-08-05 at 15:04 +0200, Geert Uytterhoeven wrote:
> It looks like you forgot to update frv? It's been failing on -next since a
> few days:
>
> kernel/locking/mcs_spinlock.h:87:2: error: implicit declaration of
> function 'cpu_relax_lowlatency'
> [-Werror=implicit-function-declaration]
Hi David,
On Mon, Jun 30, 2014 at 12:09 AM, Davidlohr Bueso wrote:
> From: Davidlohr Bueso
>
> The arch_mutex_cpu_relax() function, introduced by 34b133f, is
> hacky and ugly. It was added a few years ago to address the fact
> that common cpu_relax() calls include yielding on s390, and thus
> im
5 matches
Mail list logo