[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMzpN2gm_j-rgSV0tuAsc_TDbq4wSHWzaOhe=3ux3qWdY_TEew@mail.gmail.com>
Date: Fri, 31 Jul 2015 08:14:00 -0400
From: Brian Gerst <brgerst@...il.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: "the arch/x86 maintainers" <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>,
Denys Vlasenko <dvlasenk@...hat.com>,
Andy Lutomirski <luto@...capital.net>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 4/8] x86/vm86: Use the normal pt_regs area for vm86
On Fri, Jul 31, 2015 at 5:47 AM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * Ingo Molnar <mingo@...nel.org> wrote:
>
>>
>> > I fixed this up.
>>
>> Another build fix was needed for:
>>
>> arch/x86/mm/fault.c: In function ‘check_v8086_mode’:
>> arch/x86/mm/fault.c:319:39: error: ‘struct thread_struct’ has no member named ‘vm86’
>>
>> that's on 32-bit defconfig.
>
> A third one occurs in:
>
> drivers/scsi/dpt_i2o.c:1933:7: error: ‘CPU_386’ undeclared (first use in this function)
> drivers/scsi/dpt_i2o.c:1936:7: error: ‘CPU_486’ undeclared (first use in this function)
> drivers/scsi/dpt_i2o.c:1939:7: error: ‘CPU_586’ undeclared (first use in this function)
>
> due to the include file changes.
>
> I fixed this up too.
>
> Thanks,
>
> Ingo
I'll admit that I forgot to test the 64-bit build, but the SCSI
driver... WTF is it doing with the cpu type?
--
Brian Gerst
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists