From: Jiri Slaby <jirislaby@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: "open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Jonathan Corbet <corbet@lwn.net>, Martin Liska <mliska@suse.cz>,
Andi Kleen <ak@linux.intel.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH 0/4] kbuild: lto: documentation fixes
Date: Tue, 19 Jul 2022 09:29:28 +0200 [thread overview]
Message-ID: <292b1e65-6ac3-80c7-1ab6-c0e750fd03f4@kernel.org> (raw)
In-Reply-To: <51c4fbf0-bee9-4326-1ef0-bf2d25bde377@gmail.com>
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@gmail.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
prev parent reply other threads:[~2022-07-19 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 9:32 Bagas Sanjaya
2022-07-16 9:32 ` [PATCH 1/4] Documentation: lto: add blank line padding before single requirement list Bagas Sanjaya
2022-07-16 9:32 ` [PATCH 2/4] Documentation: lto: use bullet list for FAQ Bagas Sanjaya
2022-07-16 9:32 ` [PATCH 3/4] Documentation: lto: use bullet lists for external link references list Bagas Sanjaya
2022-07-16 9:32 ` [PATCH 4/4] Documentation: lto: add LTO documentation to toc index Bagas Sanjaya
2022-07-18 1:49 ` [PATCH 0/4] kbuild: lto: documentation fixes Masahiro Yamada
2022-07-18 7:17 ` Bagas Sanjaya
2022-07-19 7:29 ` Jiri Slaby [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=292b1e65-6ac3-80c7-1ab6-c0e750fd03f4@kernel.org \
--to=jirislaby@kernel.org \
--cc=ak@linux.intel.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mliska@suse.cz \
--cc=ndesaulniers@google.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
all inboxes | Powered by JetHome®