All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Robert Richter <robert.richter@amd.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH next&mainline] oprofile: fix build when CONFIG_PM is disabled
Date: Wed, 1 Sep 2010 09:57:08 -0700	[thread overview]
Message-ID: <20100901095708.c1027a98.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100901165002.GN22783@erda.amd.com>

On Wed, 1 Sep 2010 18:50:02 +0200 Robert Richter wrote:

> On 01.09.10 12:41:32, Randy Dunlap wrote:
> > From: Randy Dunlap <randy.dunlap@oracle.com>
> > 
> > Using do/while for a function-returning-a-value does not
> > make gcc happy, so change it to a static inline function.
> > (happens when CONFIG_PM is not enabled)
> > 
> > arch/x86/oprofile/nmi_int.c:784: error: expected expression before 'do'
> > 
> > Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> 
> I already sent a fix to Ingo that fixes this.
> 
> Will update my for-next branch as soon as it is applied in tip.

Good.

But I looked at oprofile.git and didn't see any such patch.
Did I miss it there?  Can you point me to it, please?

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2010-09-01 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01  3:36 linux-next: Tree for September 1 Stephen Rothwell
2010-09-01 16:41 ` [PATCH next&mainline] oprofile: fix build when CONFIG_PM is disabled Randy Dunlap
2010-09-01 16:50   ` Robert Richter
2010-09-01 16:57     ` Randy Dunlap [this message]
2010-09-01 19:33     ` Robert Richter
2010-09-01 16:52   ` Ingo Molnar
2010-09-02  1:38 ` linux-next: Tree for September 1 David Miller
2010-09-02  3:33   ` 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=20100901095708.c1027a98.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=robert.richter@amd.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.