public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
	Remis Lima Baima <remis.developer@googlemail.com>
Subject: Re: linux-next: asm-generic tree build failure
Date: Fri, 15 May 2009 14:53:35 +0200	[thread overview]
Message-ID: <200905151453.36277.arnd@arndb.de> (raw)
In-Reply-To: <20090515141853.59d2019b.sfr@canb.auug.org.au>

On Friday 15 May 2009, Stephen Rothwell wrote:
> Hi Arnd,
> 
> Today's linux-next build (powerpc_allnoconfig) failed like this:
> 
> arch/powerpc/mm/tlb_hash32.c:65: error: expected declaration specifiers or '...' before '(' token
> arch/powerpc/mm/tlb_hash32.c: In function 'flush_tlb_mm':
> arch/powerpc/mm/tlb_hash32.c:66: error: number of arguments doesn't match prototype
> arch/powerpc/include/asm/tlbflush.h:57: error: prototype declaration
> arch/powerpc/mm/tlb_hash32.c: At top level:
> arch/powerpc/mm/tlb_hash32.c:145: error: redefinition of 'flush_tlb_mm'
> arch/powerpc/mm/tlb_hash32.c:65: note: previous definition of 'flush_tlb_mm' was here
> 
> Caused by commit f8089f1f5eaf4925b0925e69cd311d7d1d423e6a ("asm-generic:
> Add missing generic tlb_flush definition").
> 
> I have dropped the asm-generic tree for today (since I have no earlier
> version).

Thanks for the info. I actually removed the broken commit in the version
that I sent out, but it must have crept back in during one of my merges.

I pushed out the right version now.

	Arnd <><

  reply	other threads:[~2009-05-15 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15  4:18 linux-next: asm-generic tree build failure Stephen Rothwell
2009-05-15 12:53 ` Arnd Bergmann [this message]
2009-05-16  6:44   ` Stephen Rothwell

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=200905151453.36277.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-next@vger.kernel.org \
    --cc=remis.developer@googlemail.com \
    --cc=sfr@canb.auug.org.au \
    /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