On 08/02/13 03:17, Rusty Russell wrote:
> James Hogan writes:
>> Hi Rusty,
>>
>> The metag architecture tree adds an add_taint(TAINT_DIE) like other
>> architectures do, and the modules-next tree adds the
>> LOCKDEP_NOW_UNRELIABLE flag to all uses of add_taint (but obviously
>> misses arch/metag s
Hi Vineet,
On Fri, 8 Feb 2013 10:46:24 +0530 Vineet Gupta
wrote:
>
> On Thursday 07 February 2013 04:46 PM, James Hogan wrote:
> >
> > The metag architecture tree adds an add_taint(TAINT_DIE) like other
> > architectures do, and the modules-next tree adds the
> > LOCKDEP_NOW_UNRELIABLE flag to
On Thursday 07 February 2013 04:46 PM, James Hogan wrote:
> Hi Rusty,
>
> The metag architecture tree adds an add_taint(TAINT_DIE) like other
> architectures do, and the modules-next tree adds the
> LOCKDEP_NOW_UNRELIABLE flag to all uses of add_taint (but obviously
> misses arch/metag since it do
James Hogan writes:
> Hi Rusty,
>
> The metag architecture tree adds an add_taint(TAINT_DIE) like other
> architectures do, and the modules-next tree adds the
> LOCKDEP_NOW_UNRELIABLE flag to all uses of add_taint (but obviously
> misses arch/metag since it doesn't exist yet), causing a compile er
Hi Rusty,
The metag architecture tree adds an add_taint(TAINT_DIE) like other
architectures do, and the modules-next tree adds the
LOCKDEP_NOW_UNRELIABLE flag to all uses of add_taint (but obviously
misses arch/metag since it doesn't exist yet), causing a compile error
on metag in -next when the t
5 matches
Mail list logo