From: Joel Fernandes <joel@joelfernandes.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, qais.yousef@arm.com,
dietmar.eggemann@arm.com, linux@manojrajarao.com, ast@kernel.org,
atishp04@gmail.com, dancol@google.com,
Dan Williams <dan.j.williams@intel.com>,
gregkh@linuxfoundation.org, Guenter Roeck <groeck@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
karim.yaghmour@opersys.com, Kees Cook <keescook@chromium.org>,
kernel-team@android.com, linux-doc@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-trace-devel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
mhiramat@kernel.org, rdunlap@infradead.org, rostedt@goodmis.org,
Shuah Khan <shuah@kernel.org>,
yhs@fb.com
Subject: Re: [PATCH v5 1/3] Provide in-kernel headers to make extending kernel easier
Date: Wed, 20 Mar 2019 15:42:18 -0400 [thread overview]
Message-ID: <20190320194218.GA80310@google.com> (raw)
In-Reply-To: <20190320113111.d68a7c71c2c163bbc7d5f6aa@linux-foundation.org>
On Wed, Mar 20, 2019 at 11:31:11AM -0700, Andrew Morton wrote:
> On Wed, 20 Mar 2019 12:31:14 -0400 "Joel Fernandes (Google)" <joel@joelfernandes.org> wrote:
>
> > Introduce in-kernel headers and other artifacts which are made available
> > as an archive through proc (/proc/kheaders.tar.xz file).
>
> Lazyass here hasn't been following the recent review discussion and is
> going to try cheating. Are there significant outstanding concerns now,
> or are we good to go?
Looks to me like it is pretty solid. v4->v5 was just cosmetic changes,
rebasing etc. Unless Masahiro has any other concerns, it could be a
linux-next candidate. I tested it quite heavily, but would be nice to get
some linux-next testing as well.
thanks,
- Joel
next prev parent reply other threads:[~2019-03-20 19:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 16:31 [PATCH v5 1/3] Provide in-kernel headers to make extending kernel easier Joel Fernandes (Google)
2019-03-20 16:31 ` [PATCH v5 2/3] Add selftests for module build using in-kernel headers Joel Fernandes (Google)
2019-03-20 16:31 ` [PATCH v5 3/3] init/config: Do not select BUILD_BIN2C for IKCONFIG Joel Fernandes (Google)
2019-03-20 18:31 ` [PATCH v5 1/3] Provide in-kernel headers to make extending kernel easier Andrew Morton
2019-03-20 19:42 ` Joel Fernandes [this message]
2019-04-08 16:29 ` Olof Johansson
2019-04-08 16:37 ` Daniel Colascione
2019-04-08 16:53 ` Olof Johansson
2019-04-08 20:36 ` Joel Fernandes
2019-04-10 15:07 ` Olof Johansson
2019-04-10 15:50 ` Joel Fernandes
2019-04-10 16:34 ` Olof Johansson
2019-04-10 17:33 ` Joel Fernandes
2019-04-10 17:35 ` Daniel Colascione
2019-04-11 3:15 ` Alexei Starovoitov
2019-04-11 16:30 ` Joel Fernandes
2019-04-14 19:38 ` Olof Johansson
2019-04-15 9:41 ` Enrico Weigelt, metux IT consult
2019-04-15 13:52 ` Joel Fernandes
2019-04-15 14:05 ` Joel Fernandes
2019-04-15 14:41 ` Steven Rostedt
2019-04-16 3:50 ` Kees Cook
2019-04-16 12:33 ` Steven Rostedt
2019-04-16 12:49 ` Greg Kroah-Hartman
2019-04-16 13:04 ` Joel Fernandes
2019-04-16 13:32 ` Karim Yaghmour
2019-04-16 13:45 ` Steven Rostedt
2019-04-16 14:21 ` Joel Fernandes
2019-04-16 14:22 ` Greg Kroah-Hartman
2019-04-16 14:43 ` Steven Rostedt
2019-04-16 16:42 ` Olof Johansson
2019-04-16 16:46 ` Alexei Starovoitov
2019-04-16 16:57 ` Olof Johansson
2019-04-16 17:22 ` Joel Fernandes
2019-04-16 17:30 ` Alexei Starovoitov
2019-04-16 16:47 ` Olof Johansson
2019-04-10 19:19 ` Arnd Bergmann
2019-04-12 16:16 ` Enrico Weigelt, metux IT consult
2019-04-12 17:25 ` Steven Rostedt
2019-04-08 20:52 ` Karim Yaghmour
2019-04-10 15:15 ` Olof Johansson
2019-04-10 15:44 ` Daniel Colascione
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=20190320194218.GA80310@google.com \
--to=joel@joelfernandes.org \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=atishp04@gmail.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dancol@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=karim.yaghmour@opersys.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux@manojrajarao.com \
--cc=mhiramat@kernel.org \
--cc=qais.yousef@arm.com \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=yamada.masahiro@socionext.com \
--cc=yhs@fb.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).