public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Daney <david.daney@cavium.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: David Daney <ddaney.cavm@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] recordmcount: Fix handling of elf64 big-endian objects.
Date: Fri, 06 Jan 2012 15:15:18 -0800	[thread overview]
Message-ID: <4F078086.7060208@cavium.com> (raw)
In-Reply-To: <1325891377.7642.17.camel@gandalf.stny.rr.com>

On 01/06/2012 03:09 PM, Steven Rostedt wrote:
> On Fri, 2012-01-06 at 12:42 -0800, David Daney wrote:
>
>> Any more feedback on this patch?  Should I look for it to appear in 3.3?
>
> OK, I tested it and then I noticed that mainline doesn't have
> "HAVE_C_RECORDMCOUNT" set. Is that going in the PPC tree?

I have no idea, I'm a MIPS guy at the moment.

> I added that
> to arch/powerpc/Kconfig, and did see the bug you saw. After adding your
> patch, I did a diff of the available_filter_functions and had this:
>
>> .elf_core_extra_phdrs
>> .elf_core_write_extra_phdrs
>> .elf_core_write_extra_data
>> .elf_core_extra_data_size
>
> These 4 functions were added after doing the change. Weird.
>
> Anyway, I'll run the change through my normal tests and then push it
> out.
>

Thanks,
David Daney

  reply	other threads:[~2012-01-06 23:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20  1:42 [PATCH] recordmcount: Fix handling of elf64 big-endian objects David Daney
2011-12-20  3:09 ` Steven Rostedt
2012-01-06 20:42   ` David Daney
2012-01-06 21:47     ` Steven Rostedt
2012-01-06 23:09     ` Steven Rostedt
2012-01-06 23:15       ` David Daney [this message]
2012-01-06 23:24         ` Steven Rostedt
2012-01-08 11:51 ` [tip:perf/core] " tip-bot for David Daney

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=4F078086.7060208@cavium.com \
    --to=david.daney@cavium.com \
    --cc=ddaney.cavm@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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