All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	aleksander.lobakin@intel.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v2 0/2] docs: net: page_pool: sync dev and kdoc
Date: Wed,  2 Aug 2023 09:18:19 -0700	[thread overview]
Message-ID: <20230802161821.3621985-1-kuba@kernel.org> (raw)

Document PP_FLAG_DMA_SYNC_DEV based on recent conversation.
Use kdoc to document structs and functions, to avoid duplication.

Olek, this will conflict with your work, but I think that trying
to make progress in parallel is the best course of action...
Retargetting at net-next to make it a little less bad.

Jakub Kicinski (2):
  docs: net: page_pool: document PP_FLAG_DMA_SYNC_DEV parameters
  docs: net: page_pool: use kdoc to avoid duplicating the information

 Documentation/networking/page_pool.rst | 110 +++++++++-----------
 include/net/page_pool.h                | 134 +++++++++++++++++++------
 net/core/page_pool.c                   |  31 +++++-
 3 files changed, 181 insertions(+), 94 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-08-02 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 16:18 Jakub Kicinski [this message]
2023-08-02 16:18 ` [PATCH net-next v2 1/2] docs: net: page_pool: document PP_FLAG_DMA_SYNC_DEV parameters Jakub Kicinski
2023-08-03  3:17   ` Randy Dunlap
2023-08-03  6:30   ` Michael Chan
2023-08-03  7:04   ` Jesper Dangaard Brouer
2023-08-03  9:35   ` Somnath Kotur
2023-08-02 16:18 ` [PATCH net-next v2 2/2] docs: net: page_pool: use kdoc to avoid duplicating the information Jakub Kicinski
2023-08-03  3:17   ` Randy Dunlap
2023-08-03  7:08   ` Jesper Dangaard Brouer
2023-08-03 17:10 ` [PATCH net-next v2 0/2] docs: net: page_pool: sync dev and kdoc 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=20230802161821.3621985-1-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --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.