linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	ppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: build warnings after merge of the final tree (tip treee related)
Date: Wed, 15 Sep 2010 10:29:30 +1000	[thread overview]
Message-ID: <20100915102930.5e4d59cb.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4C8FFE76.8070801@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 327 bytes --]

Hi Yinghai,

On Tue, 14 Sep 2010 16:00:06 -0700 Yinghai Lu <yinghai@kernel.org> wrote:
>
> Also, we may need to remove all extern and __init and __initdata etc in .h files.

Do not remove the "extern" key word.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2010-09-15  0:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-13  3:27 linux-next: build warnings after merge of the final tree (tip treee related) Stephen Rothwell
2010-09-13  4:14 ` Yinghai Lu
2010-09-13  4:39   ` Stephen Rothwell
2010-09-13  8:24     ` Yinghai Lu
2010-09-14  4:50       ` Stephen Rothwell
2010-09-14 23:00         ` Yinghai Lu
2010-09-15  0:29           ` Stephen Rothwell [this message]
2010-09-15  1:33             ` Yinghai Lu
2010-09-15  4:39               ` Stephen Rothwell
2010-09-15  5:00           ` Stephen Rothwell
2010-09-15  9:25             ` Ingo Molnar
2010-09-15 20:05               ` [PATCH -v4] memblock: Fix section mismatch warnings Yinghai Lu

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=20100915102930.5e4d59cb.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=yinghai@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).