From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Matt Helsley <mhelsley@vmware.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2 00/13] Cleanup recordmcount and begin objtool conversion
Date: Wed, 24 Jul 2019 12:29:29 -0500 [thread overview]
Message-ID: <20190724172929.fnh2kxsgxtcneipe@treble> (raw)
In-Reply-To: <5714C12C-D3D0-47F1-A301-908398B46F72@vmware.com>
On Wed, Jul 24, 2019 at 05:26:10PM +0000, Matt Helsley wrote:
>
>
> > On Jul 24, 2019, at 9:46 AM, Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > On Wed, 10 Jul 2019 12:19:00 -0500
> > Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> >
> >> On Wed, Jul 10, 2019 at 01:09:24PM -0400, Steven Rostedt wrote:
> >>>
> >>> Josh,
> >>>
> >>> Can you have a look at these? I can apply them if you think they are OK.
> >>
> >> Sorry for the delay. I didn't forget about it, it's just been a hectic
> >> month. I plan to give it a proper review soon (in the next week or so).
> >>
> >
> > Friendly reminder ;-)
> >
> > -- Steve
>
> Just thought I’d add:
>
> I rebased yesterday and noticed a few minor changes are needed to resolve conflicts with mainline. I will send a v3 out today with these changes:
>
> renaming elf_open to elf_read
>
> some kernel build changes (in Makefile.build)
>
> Also, I’ve finished removing all of the old recordmcount ELF wrapper code. I can send a follow-on RFC series by Friday.
Matt, thanks for your patience. As I told Steven, I'm unfortunately
very behind on reviews. Yours is (almost) at the top of the list.
--
Josh
prev parent reply other threads:[~2019-07-24 17:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 22:21 Matt Helsley
2019-06-11 22:21 ` [PATCH v2 01/13] recordmcount: Remove redundant strcmp Matt Helsley
2019-06-11 22:21 ` [PATCH v2 02/13] recordmcount: Remove uread() Matt Helsley
2019-06-11 22:21 ` [PATCH v2 03/13] recordmcount: Remove unused fd from uwrite() and ulseek() Matt Helsley
2019-06-11 22:21 ` [PATCH v2 04/13] recordmcount: Rewrite error/success handling Matt Helsley
2019-06-11 22:21 ` [PATCH v2 05/13] recordmcount: Kernel style function signature formatting Matt Helsley
2019-06-11 22:21 ` [PATCH v2 06/13] recordmcount: Kernel style formatting Matt Helsley
2019-06-11 22:21 ` [PATCH v2 07/13] recordmcount: Remove redundant cleanup() calls Matt Helsley
2019-06-11 22:21 ` [PATCH v2 08/13] recordmcount: Clarify what cleanup() does Matt Helsley
2019-06-11 22:21 ` [PATCH v2 09/13] objtool: Prepare to merge recordmcount Matt Helsley
2019-06-11 22:21 ` [PATCH v2 10/13] objtool: Make recordmcount into an objtool subcmd Matt Helsley
2019-06-11 22:21 ` [PATCH v2 11/13] objtool: recordmcount: Start using objtool's elf wrapper Matt Helsley
2019-06-11 22:21 ` [PATCH v2 12/13] objtool: recordmcount: Search for __mcount_loc before walking the sections Matt Helsley
2019-06-11 22:21 ` [PATCH v2 13/13] objtool: recordmcount: Convert do_func() relhdrs Matt Helsley
2019-07-10 17:09 ` [PATCH v2 00/13] Cleanup recordmcount and begin objtool conversion Steven Rostedt
2019-07-10 17:19 ` Josh Poimboeuf
2019-07-24 16:46 ` Steven Rostedt
2019-07-24 17:26 ` Matt Helsley
2019-07-24 17:29 ` Josh Poimboeuf [this message]
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=20190724172929.fnh2kxsgxtcneipe@treble \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhelsley@vmware.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®