mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: [PATCH] objtool: Fix memory leak in decode_instructions()
Date: Fri, 20 Oct 2017 09:24:08 +0200	[thread overview]
Message-ID: <20171020072408.6kkfh442ilbun27s@gmail.com> (raw)
In-Reply-To: <20171019153444.fm3hourp4burfaq7@treble>


* Josh Poimboeuf <jpoimboe@redhat.com> wrote:

> On Thu, Oct 19, 2017 at 05:21:06PM +0200, Ingo Molnar wrote:
> > 
> > * Josh Poimboeuf <jpoimboe@redhat.com> wrote:
> > 
> > > 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?
> > 
> > Yeah, that would be nice - that way I get your SOB which is better.
> 
> Sounds good.  And for patches which you *are* on CC, do you have a
> preference (ACK or resend with SOB)?

In general resend with SOB would be more robust for me, but as the 
objtool/x86-debuginfo maintainer it's your call really, I can certainly do both.

Thanks,

	Ingo

  reply	other threads:[~2017-10-20  7:24 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
2017-10-19 15:21     ` Ingo Molnar
2017-10-19 15:34       ` Josh Poimboeuf
2017-10-20  7:24         ` Ingo Molnar [this message]
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=20171020072408.6kkfh442ilbun27s@gmail.com \
    --to=mingo@kernel.org \
    --cc=jpoimboe@redhat.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.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
Powered by JetHome