mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: [PATCH] objtool: Fix memory leak in decode_instructions()
Date: Thu, 19 Oct 2017 09:12:08 -0500	[thread overview]
Message-ID: <20171019141208.atvlefiyopevma6c@treble> (raw)
In-Reply-To: <20171012161016.z4ytxmm2rbfiewbl@treble>

Hi Ingo,

I'm not sure if you saw the below ACK.  In general, for objtool patches
which don't have you on CC, is it ok if I just add you to CC along with
the ACK?  Or would you prefer I resend the patch to you with my SOB?

Or, would you rather I start queueing patches and doing pull requests
weekly (or so)?

Thanks!

On Thu, Oct 12, 2017 at 11:10:16AM -0500, Josh Poimboeuf wrote:
> On Thu, Oct 12, 2017 at 02:32:14PM +0530, Kamalesh Babulal wrote:
> > free the allocated insn before returning, when an error occurs
> > before adding insn to file->insn_list.
> > 
> > Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
> 
> Any chance you're working on porting objtool to ppc64le? :-)
> 
> Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>

-- 
Josh

  parent reply	other threads:[~2017-10-19 14:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-12  9:02 Kamalesh Babulal
2017-10-12 16:10 ` Josh Poimboeuf
2017-10-13  4:44   ` Kamalesh Babulal
2017-10-13  5:06     ` Josh Poimboeuf
2017-10-13  5:50       ` Kamalesh Babulal
2017-10-19 14:31         ` Josh Poimboeuf
2017-10-19 14:32           ` Josh Poimboeuf
2017-10-22  9:25             ` Kamalesh Babulal
2017-10-19 14:12   ` Josh Poimboeuf [this message]
2017-10-19 15:21     ` Ingo Molnar
2017-10-19 15:34       ` Josh Poimboeuf
2017-10-20  7:24         ` Ingo Molnar
2017-10-19 16:27 Josh Poimboeuf

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=20171019141208.atvlefiyopevma6c@treble \
    --to=jpoimboe@redhat.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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®