From: McClintock Matthew-B29882 <B29882@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/mm: Fix parse_arg build error
Date: Fri, 13 Jan 2012 20:54:13 +0000 [thread overview]
Message-ID: <CAEsOVNexxJEHB7dsR-coJcXcone5fTsw-nPiCaz0CTq1D16v4Q@mail.gmail.com> (raw)
In-Reply-To: <AD686389-E2D8-49C6-9443-FF3B33775469@kernel.crashing.org>
On Fri, Jan 13, 2012 at 2:45 PM, Kumar Gala <galak@kernel.crashing.org> wro=
te:
> On Jan 12, 2012, at 11:05 PM, Matthew McClintock wrote:
>
>> This fixes this build issue:
>>
>> arch/powerpc/mm/hugetlbpage.c: In function 'reserve_hugetlb_gpages':
>> arch/powerpc/mm/hugetlbpage.c:312:2: error: implicit declaration of func=
tion 'parse_args'
>> make[1]: *** [arch/powerpc/mm/hugetlbpage.o] Error 1
>>
>> Signed-off-by: Matthew McClintock <msm@freescale.com>
>> ---
>> This is for benh next tree
>>
>> arch/powerpc/mm/hugetlbpage.c | =A0 =A01 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> This is fixed upstream, benh's tree is based on a older snapshot of linus=
's tree that doesn't have this fix.
>
> commit 13020be8be2d5843c3810169cdbcc51f07ff020f
> Author: Kumar Gala <galak@kernel.crashing.org>
> Date: =A0 Thu Nov 24 09:40:07 2011 +0000
>
> =A0 =A0powerpc: Fix compiliation with hugetlbfs enabled
I was starting to realize this today after I saw Ben's pull request...
-M=
prev parent reply other threads:[~2012-01-13 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 5:05 [PATCH] powerpc/mm: Fix parse_arg build error Matthew McClintock
2012-01-13 20:45 ` Kumar Gala
2012-01-13 20:54 ` McClintock Matthew-B29882 [this message]
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=CAEsOVNexxJEHB7dsR-coJcXcone5fTsw-nPiCaz0CTq1D16v4Q@mail.gmail.com \
--to=b29882@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.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).