From: Akira Yokosawa <akiyks@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jakub Kicinski <kuba@kernel.org>
Cc: EDAC Mailing List <linux-edac@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Ignacio Encinas Rubio <ignacio@iencinas.com>,
Marco Elver <elver@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Donald Hunter <donald.hunter@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Jan Stancek <jstancek@redhat.com>,
Paolo Abeni <pabeni@redhat.com>,
Ruben Wauters <rubenru09@aol.com>,
linux-kernel-mentees@lists.linux.dev, netdev@vger.kernel.org,
Breno Leitao <leitao@debian.org>,
Randy Dunlap <rdunlap@infradead.org>,
Simon Horman <horms@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [GIT PULL for v6.17-rc2] add a generic yaml parser integrated with Netlink specs generation
Date: Wed, 13 Aug 2025 11:49:50 +0900 [thread overview]
Message-ID: <9c4a655e-095b-45fe-b35d-c3f0ae6a9237@gmail.com> (raw)
In-Reply-To: <87h5ycfl3s.fsf@trenco.lwn.net>
[-CC: LKMM folks and list; this has nothing to do with the memory model]
Hi Jon,
On Tue, 12 Aug 2025 12:31:03 -0600, Jonathan Corbet wrote:
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> writes:
>
>> Hi Jon/Jakub,
>>
>> In case you both prefer to merge from a stable tag, please pull from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-docs.git docs/v6.17-1
>>
>> For:
>>
>> - An YAML parser Sphinx plugin, integrated with Netlink YAML doc
>> parser.
>
> OK, I have done that. I will note that it adds a warning:
>
>> Documentation/networking/netlink_spec/index.rst: WARNING: document isn't included in any toctree
>
> ...it might be nice to get that straightened out.
After the merge, "git status" complains:
Untracked files:
(use "git add <file>..." to include in what will be committed)
Documentation/networking/netlink_spec/
So, I don't think there is anything you can do in the Git repo side ...
We need to remember to "rm -rf" the directory after crossing this merge
point.
In theory, such "rm -rf" could be added somewhere in Documentation/Makefile,
but that would not work well with write-protected shared kernel repos.
Thanks, Akira
next prev parent reply other threads:[~2025-08-13 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 9:33 [GIT PULL for v6.17-rc2] add a generic yaml parser integrated with Netlink specs generation Mauro Carvalho Chehab
2025-08-12 17:43 ` Jakub Kicinski
2025-08-12 18:31 ` Jonathan Corbet
2025-08-12 18:41 ` Randy Dunlap
2025-08-12 19:23 ` Mauro Carvalho Chehab
2025-08-13 2:49 ` Akira Yokosawa [this message]
2025-08-13 7:15 ` Mauro Carvalho Chehab
2025-08-15 0:40 ` patchwork-bot+netdevbpf
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=9c4a655e-095b-45fe-b35d-c3f0ae6a9237@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=elver@google.com \
--cc=horms@kernel.org \
--cc=ignacio@iencinas.com \
--cc=jstancek@redhat.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rubenru09@aol.com \
--cc=skhan@linuxfoundation.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).