linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Julien Thierry <jthierry@redhat.com>,
	linux-kernel@vger.kernel.org, raphael.gault@arm.com
Subject: Re: [PATCH v2 00/10] Objtool updates for easier portability
Date: Thu, 2 Apr 2020 20:30:04 +0200	[thread overview]
Message-ID: <20200402183004.GJ20730@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200402175827.kk7su6mo42aa6bh5@treble>

On Thu, Apr 02, 2020 at 12:58:27PM -0500, Josh Poimboeuf wrote:
> On Fri, Mar 27, 2020 at 03:28:37PM +0000, Julien Thierry wrote:
> > Hi,
> > 
> > This patchset includes some of the least controversial changes that
> > were needed as part of the arm64 port [1].
> > 
> > I'm resending these rebase on top of linux-tip/core/objtool, following
> > the addition of Peter's patches [2]
> > 
> > It consist mostly of small fixes or lifting some limitations to make it
> > easier to support a new architecture in objtool. Of course, these will
> > not be the only required changes, but these are the ones I hope make
> > enough sense to be merged separately from the rest of arm64 port series.
> > 
> > Changes since v1[3]:
> > - Really just rebased things
> > 
> > [1] https://lkml.org/lkml/2020/1/9/643
> > [2] https://lkml.org/lkml/2020/3/25/807
> > [3] https://www.spinics.net/lists/kernel/msg3453718.html
> > 
> > Thanks,
> > 
> > Julien
> 
> I'm taking everything except 5, 7, and 10.  I'll run them through
> testing and then send them along to the tip maintainers.  Thanks!

For that set:

Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>


  reply	other threads:[~2020-04-02 18:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 15:28 [PATCH v2 00/10] Objtool updates for easier portability Julien Thierry
2020-03-27 15:28 ` [PATCH v2 01/10] objtool: Move header sync-check ealier in build Julien Thierry
2020-04-01 12:32   ` Miroslav Benes
2020-04-01 12:44     ` Julien Thierry
2020-04-01 12:55       ` Miroslav Benes
2020-04-02 17:12   ` Josh Poimboeuf
2020-04-02 17:17     ` Josh Poimboeuf
2020-03-27 15:28 ` [PATCH v2 02/10] objtool: check: Remove redundant checks on operand type Julien Thierry
2020-03-27 15:28 ` [PATCH v2 03/10] objtool: check: Clean instruction state before each function validation Julien Thierry
2020-03-27 15:28 ` [PATCH v2 04/10] objtool: check: Ignore empty alternative groups Julien Thierry
2020-04-01 12:53   ` Miroslav Benes
2020-04-01 13:43     ` Julien Thierry
2020-04-01 13:48       ` Miroslav Benes
2020-03-27 15:28 ` [PATCH v2 05/10] objtool: check: Remove check preventing branches within alternative Julien Thierry
2020-05-01 18:22   ` [tip: objtool/core] objtool: " tip-bot2 for Julien Thierry
2020-03-27 15:28 ` [PATCH v2 06/10] objtool: check: Use arch specific values in restore_reg() Julien Thierry
2020-03-27 15:28 ` [PATCH v2 07/10] objtool: check: Allow save/restore hint in non standard function symbols Julien Thierry
2020-04-01 13:54   ` Miroslav Benes
2020-04-01 14:06     ` Julien Thierry
2020-03-27 15:28 ` [PATCH v2 08/10] objtool: Add abstraction for computation of symbols offsets Julien Thierry
2020-03-27 15:28 ` [PATCH v2 09/10] objtool: Split generic and arch specific CFI definitions Julien Thierry
2020-03-27 15:28 ` [PATCH v2 10/10] objtool: Support multiple stack_op per instruction Julien Thierry
2020-04-02 17:54   ` Josh Poimboeuf
2020-04-02 18:25     ` Peter Zijlstra
2020-04-03  8:01     ` Julien Thierry
2020-04-03 14:55       ` Josh Poimboeuf
2020-04-22 22:24   ` [tip: objtool/core] " tip-bot2 for Julien Thierry
2020-04-23  7:49   ` tip-bot2 for Julien Thierry
2020-04-23 11:15     ` Peter Zijlstra
2020-04-02 17:58 ` [PATCH v2 00/10] Objtool updates for easier portability Josh Poimboeuf
2020-04-02 18:30   ` Peter Zijlstra [this message]
2020-04-03  7:17     ` Miroslav Benes

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=20200402183004.GJ20730@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=jpoimboe@redhat.com \
    --cc=jthierry@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raphael.gault@arm.com \
    /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;
as well as URLs for NNTP newsgroup(s).