From: Jakub Kicinski <kuba@kernel.org>
To: Kuniyuki Iwashima <kuniyu@amazon.co.jp>
Cc: <andrew@lunn.ch>, <bpf@vger.kernel.org>, <corbet@lwn.net>,
<davem@davemloft.net>, <f.fainelli@gmail.com>,
<linux-doc@vger.kernel.org>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>
Subject: Re: [PATCH net 00/13] docs: update and move the netdev-FAQ
Date: Mon, 28 Mar 2022 21:52:47 -0700 [thread overview]
Message-ID: <20220328215247.69d31c4a@kernel.org> (raw)
In-Reply-To: <20220329043808.95053-1-kuniyu@amazon.co.jp>
On Tue, 29 Mar 2022 13:38:08 +0900 Kuniyuki Iwashima wrote:
> From: Jakub Kicinski <kuba@kernel.org>
> Date: Sat, 26 Mar 2022 19:53:47 -0700
> > A section of documentation for tree-specific process quirks had
> > been created a while back. There's only one tree in it, so far,
> > the tip tree, but the contents seem to answer similar questions
> > as we answer in the netdev-FAQ. Move the netdev-FAQ.
> >
> > Take this opportunity to touch up and update a few sections.
>
> Thanks for update!
>
> I would like to clarify one thing about this website.
>
> http://vger.kernel.org/~davem/net-next.html
>
> I often check this before submitting patches. I like this much, but it
> seems not working properly for now. Is this no longer maintained or by
> coincidence this time? If I could help something, please let me know :)
Sorry about that, DaveM has been traveling during this merge window.
He said he'll fix it soon.
next prev parent reply other threads:[~2022-03-29 4:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-27 2:53 [PATCH net 00/13] docs: update and move the netdev-FAQ Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 01/13] docs: netdev: replace references to old archives Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 02/13] docs: netdev: minor reword Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 03/13] docs: netdev: move the patch marking section up Jakub Kicinski
2022-03-27 16:28 ` Andrew Lunn
2022-03-28 17:38 ` Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 04/13] docs: netdev: turn the net-next closed into a Warning Jakub Kicinski
2022-03-27 16:35 ` Andrew Lunn
2022-03-29 8:06 ` Martin Habets
2022-03-27 2:53 ` [PATCH net 05/13] docs: netdev: shorten the name and mention msgid for patch status Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 06/13] docs: netdev: rephrase the 'Under review' question Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 07/13] docs: netdev: rephrase the 'should I update patchwork' question Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 08/13] docs: netdev: add a question about re-posting frequency Jakub Kicinski
2022-03-27 16:40 ` Andrew Lunn
2022-03-27 2:53 ` [PATCH net 09/13] docs: netdev: make the testing requirement more stringent Jakub Kicinski
2022-03-27 16:42 ` Andrew Lunn
2022-03-28 17:51 ` Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 10/13] docs: netdev: add missing back ticks Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 11/13] docs: netdev: call out the merge window in tag checking Jakub Kicinski
2022-03-27 2:53 ` [PATCH net 12/13] docs: netdev: broaden the new vs old code formatting guidelines Jakub Kicinski
2022-03-27 2:54 ` [PATCH net 13/13] docs: netdev: move the netdev-FAQ to the process pages Jakub Kicinski
2022-03-29 4:38 ` [PATCH net 00/13] docs: update and move the netdev-FAQ Kuniyuki Iwashima
2022-03-29 4:52 ` Jakub Kicinski [this message]
2022-03-29 7:22 ` Kuniyuki Iwashima
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=20220328215247.69d31c4a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuniyu@amazon.co.jp \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.