All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
Cc: Michael Neuling <mikey@neuling.org>,
	galak@kernel.crashing.org,
	Becky Bruce <beckyb@kernel.crashing.org>,
	linux-next@vger.kernel.org, linuxppc-dev@ozlabs.org,
	McClintock Matthew-B29882 <B29882@freescale.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Pawel Moll <pawel.moll@arm.com>
Subject: Re: [PATCH] params: Fix parse_args() use in PowerPC's reserve_hugetlb_gpages()
Date: Mon, 20 Feb 2012 11:56:13 +1030	[thread overview]
Message-ID: <87aa4e8fd6.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1329494916-20575-1-git-send-email-pawel.moll@arm.com>

On Fri, 17 Feb 2012 16:08:36 +0000, Pawel Moll <pawel.moll@arm.com> wrote:
> Commit b8076966e8e1 ("params: <level>_initcall-like kernel parameters")
> changed the parse_args() API without fixing all the callers. Done now.
> 
> Signed-off-by: Pawel Moll <pawel.moll@arm.com>

Thanks Stephen, Pawel.

Applied,
Rusty.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Pawel Moll <pawel.moll@arm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Michael Neuling <mikey@neuling.org>,
	Pawel Moll <pawel.moll@arm.com>,
	linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
	McClintock Matthew-B29882 <B29882@freescale.com>
Subject: Re: [PATCH] params: Fix parse_args() use in PowerPC's reserve_hugetlb_gpages()
Date: Mon, 20 Feb 2012 11:56:13 +1030	[thread overview]
Message-ID: <87aa4e8fd6.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1329494916-20575-1-git-send-email-pawel.moll@arm.com>

On Fri, 17 Feb 2012 16:08:36 +0000, Pawel Moll <pawel.moll@arm.com> wrote:
> Commit b8076966e8e1 ("params: <level>_initcall-like kernel parameters")
> changed the parse_args() API without fixing all the callers. Done now.
> 
> Signed-off-by: Pawel Moll <pawel.moll@arm.com>

Thanks Stephen, Pawel.

Applied,
Rusty.

  reply	other threads:[~2012-02-20  3:48 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
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 [this message]
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=87aa4e8fd6.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --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 \
    --cc=mikey@neuling.org \
    --cc=pawel.moll@arm.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 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.