[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <292b1e65-6ac3-80c7-1ab6-c0e750fd03f4@kernel.org>
Date: Tue, 19 Jul 2022 09:29:28 +0200
From: Jiri Slaby <jirislaby@...nel.org>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Masahiro Yamada <masahiroy@...nel.org>
Cc: "open list:DOCUMENTATION" <linux-doc@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Jonathan Corbet <corbet@....net>,
Martin Liska <mliska@...e.cz>, Andi Kleen <ak@...ux.intel.com>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>
Subject: Re: [PATCH 0/4] kbuild: lto: documentation fixes
On 18. 07. 22, 9:17, Bagas Sanjaya wrote:
> On 7/18/22 08:49, Masahiro Yamada wrote:
>> On Sat, Jul 16, 2022 at 6:33 PM Bagas Sanjaya <bagasdotme@...il.com> wrote:
>>>
>>> Here is documentation fixes for kbuild LTO feature tree [1]. Two patches
>>> fixes warnings reported by kernel test robot, the others are formatting
>>> improvements.
>>
>>
>> Please do not submit patches unrelated to the mainline.
>>
>> This series applies to the individual repository of Jiri Slaby.
>>
>
> Seems like you missed the wording on cover letter, which said:
>
>> Here is documentation fixes for kbuild LTO feature tree [1]
>
> with link to the target tree, which is another way to say "The
> series is applied on top of this tree, not the mainline".
Yeah, but why to send the patches to all those people provided they have
no idea such a tree and changes exist at all?
Anyway, applied to my tree.
thanks,
--
js
Powered by blists - more mailing lists