[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200818130045.7bb13992@oasis.local.home>
Date: Tue, 18 Aug 2020 13:00:45 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: Masami Hiramatsu <mhiramat@...nel.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Andi Kleen <ak@...ux.intel.com>,
Ard Biesheuvel <ardb@...nel.org>, Jessica Yu <jeyu@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Mike Rapoport <rppt@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Russell King <linux@...linux.org.uk>,
Will Deacon <will@...nel.org>, Ingo Molnar <mingo@...hat.com>
Subject: Re: [PATCH] kprobes: Use module_name() macro
On Tue, 18 Aug 2020 19:33:56 +0300
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com> wrote:
> > Acked-by: Masami Hiramatsu <mhiramat@...nel.org>
>
> Great, thank you.
>
> When this might get included to a PR, or at minimum land to linux-next?
>
> Just thinking what to use as the baseline for the next version of my
> main series.
I can apply this to my tree along with Masami's latest bootconfig
patches. This will be for linux-next. I don't usually push to
linux-next until around -rc3. Would that be too late?
-- Steve
Powered by blists - more mailing lists