All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Christian Brauner <christian.brauner@ubuntu.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	linux@rasmusvillemoes.dk, cyphar@cyphar.com,
	keescook@chromium.org
Subject: Re: linux-next: Tree for Oct 18 (objtool)
Date: Tue, 22 Oct 2019 09:40:34 +0200	[thread overview]
Message-ID: <20191022074034.GK1817@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191021193652.lfccehm37dkkofp7@wittgenstein>

On Mon, Oct 21, 2019 at 09:36:53PM +0200, Christian Brauner wrote:
> Ok, so I take it you route that patch somehwere through tip?
> I'm happy with the ubsan fix:

Yeah, I'll go make a real patch with Changelog of it and stick it in
tip.

> Acked-by: Christian Brauner <christian.brauner@ubuntu.com>

Thanks!

  reply	other threads:[~2019-10-22  7:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  7:03 linux-next: Tree for Oct 18 Stephen Rothwell
2019-10-18 15:33 ` linux-next: Tree for Oct 18 (objtool) Randy Dunlap
2019-10-21 12:35   ` Peter Zijlstra
2019-10-21 13:11     ` Peter Zijlstra
2019-10-21 13:19       ` Christian Brauner
2019-10-21 13:47         ` Peter Zijlstra
2019-10-21 19:36           ` Christian Brauner
2019-10-22  7:40             ` Peter Zijlstra [this message]
2019-10-22  8:02               ` Christian Brauner
2019-10-21 15:59       ` Randy Dunlap
2019-10-28 11:42       ` [tip: x86/asm] ubsan, x86: Annotate and allow __ubsan_handle_shift_out_of_bounds() in uaccess regions tip-bot2 for Peter Zijlstra

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=20191022074034.GK1817@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=christian.brauner@ubuntu.com \
    --cc=cyphar@cyphar.com \
    --cc=jpoimboe@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.