[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170119085214.GG6485@twins.programming.kicks-ass.net>
Date: Thu, 19 Jan 2017 09:52:14 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Kees Cook <keescook@...omium.org>,
Elena Reshetova <elena.reshetova@...el.com>,
"kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>,
Arnd Bergmann <arnd@...db.de>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <h.peter.anvin@...el.com>,
Will Deacon <will.deacon@....com>,
David Windsor <dwindsor@...il.com>
Subject: Re: [RFCv2 PATCH 00/18] refcount_t API + usage
On Wed, Jan 18, 2017 at 09:35:34PM +0100, Greg KH wrote:
> I think the refcount_t patch should also go to tip given it depends on
> the kref patches. But that's up to Peter, he would know best...
Yeah, so I held back on that and the kref conversion, because I wanted
to get the kref fixup thingies in first. If there's no fallout from that
I can stuff in the refcount_t bits.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
