From: Shuah Khan <skhan@linuxfoundation.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Shuah Khan <shuah@kernel.org>, Kees Cook <keescook@chromium.org>,
Anders Roxell <anders.roxell@linaro.org>,
Tim Bird <Tim.Bird@sony.com>,
kernel@collabora.com,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] Makefile: replace headers_install with headers for kselftest
Date: Tue, 26 Jul 2022 18:13:54 -0600 [thread overview]
Message-ID: <8a3c18c5-2abc-9ea2-0867-95b31d45da1d@linuxfoundation.org> (raw)
In-Reply-To: <81241d70-7952-2f55-9181-d18679068998@collabora.com>
On 7/19/22 11:31 AM, Guillaume Tucker wrote:
> On 19/07/2022 17:06, Masahiro Yamada wrote:
>> On Tue, Jul 19, 2022 at 9:37 PM Guillaume Tucker
>> <guillaume.tucker@collabora.com> wrote:
>>>
>>>
>>> Masahiro-san,
>>>
>>> A you OK with applying this in the kbuild tree ahead of the
>>> upcoming merge window?
>>
>>
>> No.
>>
>> This is a fix-up patch on top of the previous one [1],
>> which was applied to the kselftest tree.
>>
>> This cannot apply to the kbuild tree.
>
> OK thank you for confirming.
>
> Shuah, I guess you're happy to apply it to the kselftest tree
> instead then?
>
Sorry for a late response due to time off. Working through my Inbox.
Applied now to linux-kselftest next for 5.20-rc1.
thanks,
-- Shuah
prev parent reply other threads:[~2022-07-27 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 6:33 [PATCH] Makefile: replace headers_install with headers for kselftest Guillaume Tucker
2022-07-14 20:45 ` Shuah Khan
2022-07-19 12:37 ` Guillaume Tucker
2022-07-19 15:06 ` Masahiro Yamada
2022-07-19 17:31 ` Guillaume Tucker
2022-07-27 0:13 ` Shuah Khan [this message]
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=8a3c18c5-2abc-9ea2-0867-95b31d45da1d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Tim.Bird@sony.com \
--cc=anders.roxell@linaro.org \
--cc=guillaume.tucker@collabora.com \
--cc=keescook@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=shuah@kernel.org \
/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).