public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Cree <mcree@orcon.net.nz>
To: Matt Turner <mattst88@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Borislav Petkov <borislav.petkov@amd.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-alpha@vger.kernel.org
Subject: Re: 2.6.35-rc2 compilation error on Alpha
Date: Mon, 07 Jun 2010 13:13:12 +1200	[thread overview]
Message-ID: <4C0C47A8.1000800@orcon.net.nz> (raw)
In-Reply-To: <AANLkTim9aWVzb7v5fnS6x3ghMU2_tpaLlbZu3SKXV_0R@mail.gmail.com>

On 07/06/10 12:08, Matt Turner wrote:
> On Sun, Jun 6, 2010 at 6:35 PM, Michael Cree<mcree@orcon.net.nz>  wrote:
>> When compiling 2.6.35-rc2 for Alpha architecture the following compiler
>> error is seen:
>>
>>   CC      arch/alpha/kernel/asm-offsets.s
>> In file included from include/linux/kernel.h:17,
>>                  from include/linux/sched.h:54,
>>                  from arch/alpha/kernel/asm-offsets.c:9:
>> include/linux/bitops.h: In function ‘hweight_long’:
>> include/linux/bitops.h:49: error: implicit declaration of function
>> ‘__arch_hweight32’
>
> Yeah, it was a stupid typo in
> 1527bc8b928dd1399c3d3467dd47d9ede210978a. I've fixed it and put the
> patch in my tree for Linus.

Ah, now the offending commit is pointed out to me I can see the trivial 
fix.  With that, as you say, compilation now bombs out in the pci-sysfs 
stuff.  Since you claim to have that in hand I'll await your solution.

Cheers
Michael.

  reply	other threads:[~2010-06-07  1:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-06 22:35 2.6.35-rc2 compilation error on Alpha Michael Cree
2010-06-07  0:08 ` Matt Turner
2010-06-07  1:13   ` Michael Cree [this message]
2010-06-07  1:24     ` Matt Turner
2010-06-07  3:04       ` Greg KH
2010-06-08 17:24       ` Chris Wright

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=4C0C47A8.1000800@orcon.net.nz \
    --to=mcree@orcon.net.nz \
    --cc=borislav.petkov@amd.com \
    --cc=hpa@zytor.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.com \
    /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