public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	Andy Lutomirski <luto@amacapital.net>,
	David Daney <david.daney@cavium.com>
Subject: Re: [PATCH] mips: Fix build if PERF_EVENTS is configured
Date: Wed, 08 Apr 2015 20:40:08 -0700	[thread overview]
Message-ID: <5525F498.5040203@roeck-us.net> (raw)
In-Reply-To: <20150409000934.GA21107@linux-mips.org>

On 04/08/2015 05:09 PM, Ralf Baechle wrote:
> On Wed, Apr 08, 2015 at 01:29:52PM -0700, Guenter Roeck wrote:
>
>> mips builds fail in -next as follows if PERF_EVENTS is configured.
>>
>> kernel/built-in.o: In function `perf_sample_regs_user':
>> kernel/events/core.c:4828: undefined reference to `perf_get_regs_user'
>>
>> The problem is caused by commit 3478e32c1545 ("MIPS: Add user stack and
>> registers to perf.") in combination with commit 88a7c26af8da ("perf:
>> Move task_pt_regs sampling into arch code"), which introduces
>> perf_get_regs_user().
>>
>> Cc: Andy Lutomirski <luto@amacapital.net>
>> Cc: David Daney <david.daney@cavium.com>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>
> I've already applied the same change locally but due to patch ordering
> constraints I'm considering to temporarily pull this patch until the
> perf stuff and the remainder of the MIPS changes are in 4.1 or so.
>
Hi Ralf,

Does it hurt to have the function if 88a7c26af8da is not in the tree ?
Sure, you'll get a smatch and/or sparse warning, but I would consider that
to be less severe than build failures.

Thanks,
Guenter


  reply	other threads:[~2015-04-09  3:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 20:29 [PATCH] mips: Fix build if PERF_EVENTS is configured Guenter Roeck
2015-04-09  0:09 ` Ralf Baechle
2015-04-09  3:40   ` Guenter Roeck [this message]
2015-04-10 14:05     ` Ralf Baechle

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=5525F498.5040203@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=david.daney@cavium.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=luto@amacapital.net \
    --cc=ralf@linux-mips.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