From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-6.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_HI autolearn=unavailable autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id B8F757D04D for ; Wed, 20 Mar 2019 19:42:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725988AbfCTTmY (ORCPT ); Wed, 20 Mar 2019 15:42:24 -0400 Received: from mail-qk1-f196.google.com ([209.85.222.196]:36716 "EHLO mail-qk1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726823AbfCTTmV (ORCPT ); Wed, 20 Mar 2019 15:42:21 -0400 Received: by mail-qk1-f196.google.com with SMTP id k130so14916655qke.3 for ; Wed, 20 Mar 2019 12:42:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=VbrnenGSNs7Bb+kAyHYWxxdHjU+QoptUXg7QX+PaZ/Y=; b=HXQgE8zfQxOptIu1OfFHgkh1M4Y85bpzO+ebVd4rPpXL49zCno2cViFhK0erMuRplB bceo3+yUwbJNYNi49nF27k4owhMHCyk+Ozc9aAnPDIr+8dvvikp+w6dkudHZ7QibukjG of1vSuPT4BErfsZIRPRxCHT+QKbxBxYZQ7KQI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=VbrnenGSNs7Bb+kAyHYWxxdHjU+QoptUXg7QX+PaZ/Y=; b=mbDCLeBKRSKZGPgOlZl0RzKckwdwXq2ZYJUWrbtuiEcKhVoAgQ0NLEDzjlQ6vhBDQa LF+jRuFaeks5rm4GI2cyxnFE9mYbhRZ2+AU1eDkEtr8KlVNZreTNZyqHxQSHBBt7Y35R sBIzRbXxUqiDCIT57zBRRvpvfB0Z4+orCivmkDMd2gfzQwahy3a/b36BGyQtsJ/CgYIf H8I4a6YWGddyxgYvR/Vd2j/zoHTRpMMkFcuxsZ8vHi5ueH+A8zhMQEEzOwODbnMozGhO 1/Ckp1AKHWiJB0woeU+ETXOeJAZJ+477h0ASvnosruLyLaW6QrDzCxugQIjgqhAh79vz JsvA== X-Gm-Message-State: APjAAAVBR3Q1/e9Ul+AbujZvwNLmVZ4XFP1ms2ysKkPdaXplJigkiFbb dvuunMdlcFHUZ3ckJvFIvQT1uA== X-Google-Smtp-Source: APXvYqwcB37vMB2GCE52Uua6m/iA9pSMhkqnSfm0d418ctJ/k3gXQolJrEwPE58AnsbdheKSey46zw== X-Received: by 2002:a37:6510:: with SMTP id z16mr7531586qkb.341.1553110939836; Wed, 20 Mar 2019 12:42:19 -0700 (PDT) Received: from localhost ([2620:0:1004:1100:cca9:fccc:8667:9bdc]) by smtp.gmail.com with ESMTPSA id r64sm1481783qkc.27.2019.03.20.12.42.18 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 20 Mar 2019 12:42:18 -0700 (PDT) Date: Wed, 20 Mar 2019 15:42:18 -0400 From: Joel Fernandes To: Andrew Morton 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 , gregkh@linuxfoundation.org, Guenter Roeck , Jonathan Corbet , karim.yaghmour@opersys.com, Kees Cook , kernel-team@android.com, linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-trace-devel@vger.kernel.org, Masahiro Yamada , mhiramat@kernel.org, rdunlap@infradead.org, rostedt@goodmis.org, Shuah Khan , yhs@fb.com Subject: Re: [PATCH v5 1/3] Provide in-kernel headers to make extending kernel easier Message-ID: <20190320194218.GA80310@google.com> References: <20190320163116.39275-1-joel@joelfernandes.org> <20190320113111.d68a7c71c2c163bbc7d5f6aa@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190320113111.d68a7c71c2c163bbc7d5f6aa@linux-foundation.org> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.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)" 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