netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, f.fainelli@gmail.com, rdunlap@infradead.org
Subject: Re: [PATCH net 0/2] netdev doc de-FAQization
Date: Wed, 21 Dec 2022 23:20:58 +0100	[thread overview]
Message-ID: <Y6OGyrmLKqy51k6K@lunn.ch> (raw)
In-Reply-To: <20221221184007.1170384-1-kuba@kernel.org>

On Wed, Dec 21, 2022 at 10:40:05AM -0800, Jakub Kicinski wrote:
> I've been tempted to do this for a while. I think that we have outgrown
> the FAQ format for our process doc. I'm curious what others think but
> I often find myself struggling to locate information in this doc,
> because the questions do not serve well as section headers.

Looks good to me. It has grown beyond a simple FAQ.

I think you kept the top level header 'netdev FAQ'. Do we also want to
change that, since it is no longer question/answer formatted? Not that
i have a good idea what to call it instead.

Anyway:

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  parent reply	other threads:[~2022-12-21 22:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 18:40 [PATCH net 0/2] netdev doc de-FAQization Jakub Kicinski
2022-12-21 18:40 ` [PATCH net 1/2] docs: netdev: reshuffle sections in prep for de-FAQization Jakub Kicinski
2022-12-21 18:40 ` [PATCH net 2/2] docs: netdev: convert to a non-FAQ document Jakub Kicinski
2022-12-21 21:35 ` [PATCH net 0/2] netdev doc de-FAQization Randy Dunlap
2022-12-21 22:20 ` Andrew Lunn [this message]
2022-12-22  1:11   ` Jakub Kicinski

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=Y6OGyrmLKqy51k6K@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rdunlap@infradead.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).