All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "galak@kernel.crashing.org" <galak@kernel.crashing.org>,
	Becky Bruce <beckyb@kernel.crashing.org>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: Build fail in hugetlbpage.c with linux-next and mpc85xx_defconfig
Date: Thu, 16 Feb 2012 10:37:43 +1100	[thread overview]
Message-ID: <16098.1329349063@neuling.org> (raw)
In-Reply-To: <CAEsOVNcpBLmsmyZLW2HNe3MDR5cx5oJnPMmGD6Mqz4AjG16=9A@mail.gmail.com>

> > Becky,
> >
> > This has been broken in linux-next for a while. =A0Looks like a merge
> > issue but you were the last to touch it...
> >
> > arch/powerpc/mm/hugetlbpage.c: In function 'reserve_hugetlb_gpages':
> > arch/powerpc/mm/hugetlbpage.c:313: error: passing argument 5 of 'parse_ar=
> gs' makes integer from pointer without a cast
> > include/linux/moduleparam.h:317: note: expected 's16' but argument is of =
> type 'int (*)(char *, char *)'
> > arch/powerpc/mm/hugetlbpage.c:313: error: too few arguments to function '=
> parse_args'
> 
> A suggest fix has been submitted.

Do you have a link?  Which tree is it going in?

Mikey

WARNING: multiple messages have this Message-ID (diff)
From: Michael Neuling <mikey@neuling.org>
To: McClintock Matthew-B29882 <B29882@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: Build fail in hugetlbpage.c with linux-next and mpc85xx_defconfig
Date: Thu, 16 Feb 2012 10:37:43 +1100	[thread overview]
Message-ID: <16098.1329349063@neuling.org> (raw)
In-Reply-To: <CAEsOVNcpBLmsmyZLW2HNe3MDR5cx5oJnPMmGD6Mqz4AjG16=9A@mail.gmail.com>

> > Becky,
> >
> > This has been broken in linux-next for a while. =A0Looks like a merge
> > issue but you were the last to touch it...
> >
> > arch/powerpc/mm/hugetlbpage.c: In function 'reserve_hugetlb_gpages':
> > arch/powerpc/mm/hugetlbpage.c:313: error: passing argument 5 of 'parse_ar=
> gs' makes integer from pointer without a cast
> > include/linux/moduleparam.h:317: note: expected 's16' but argument is of =
> type 'int (*)(char *, char *)'
> > arch/powerpc/mm/hugetlbpage.c:313: error: too few arguments to function '=
> parse_args'
> 
> A suggest fix has been submitted.

Do you have a link?  Which tree is it going in?

Mikey

  reply	other threads:[~2012-02-15 23:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15 23:08 Build fail in hugetlbpage.c with linux-next and mpc85xx_defconfig Michael Neuling
2012-02-15 23:08 ` Michael Neuling
2012-02-15 23:28 ` [PATCH] powerpc/hugepage: Fix missing header file for parse_args Matthew McClintock
2012-02-15 23:28   ` Matthew McClintock
2012-02-15 23:32 ` Build fail in hugetlbpage.c with linux-next and mpc85xx_defconfig McClintock Matthew-B29882
2012-02-15 23:32   ` McClintock Matthew-B29882
2012-02-15 23:37   ` Michael Neuling [this message]
2012-02-15 23:37     ` Michael Neuling
2012-02-15 23:40     ` McClintock Matthew-B29882
2012-02-15 23:40       ` McClintock Matthew-B29882
2012-02-16  5:01       ` Michael Neuling
2012-02-16  5:03         ` McClintock Matthew-B29882
2012-02-16  5:03           ` McClintock Matthew-B29882
2012-02-16  0:15 ` Stephen Rothwell
2012-02-16  0:15   ` Stephen Rothwell
2012-02-16  2:14   ` Stephen Rothwell
2012-02-16  2:14     ` Stephen Rothwell
2012-02-17 16:08   ` [PATCH] params: Fix parse_args() use in PowerPC's reserve_hugetlb_gpages() Pawel Moll
2012-02-17 16:08     ` Pawel Moll
2012-02-20  1:26     ` Rusty Russell
2012-02-20  1:26       ` Rusty Russell

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=16098.1329349063@neuling.org \
    --to=mikey@neuling.org \
    --cc=B29882@freescale.com \
    --cc=beckyb@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.