From: Jakub Kicinski <kuba@kernel.org>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Kees Cook <keescook@chromium.org>,
netdev@vger.kernel.org, Alexander Duyck <alexanderduyck@fb.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Eric Dumazet <edumazet@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Yunsheng Lin <linyunsheng@huawei.com>,
intel-wired-lan@lists.osuosl.org,
nex.sw.ncis.osdt.itp.upstreaming@intel.com,
Christoph Lameter <cl@linux.com>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Vlastimil Babka <vbabka@suse.cz>,
Jesper Dangaard Brouer <hawk@kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH net-next v9 7/9] libeth: add Rx buffer management
Date: Thu, 11 Apr 2024 06:45:41 -0700 [thread overview]
Message-ID: <20240411064541.7106be9a@kernel.org> (raw)
In-Reply-To: <d28896e5-32cd-4376-bb1e-44c9dbfea172@intel.com>
On Thu, 11 Apr 2024 11:07:24 +0200 Alexander Lobakin wrote:
> > I think doc tree is a strong candidate, or at least we should not
> > merge without consulting Jon. Please post and we'll figure it out.
>
> Can this series go simultaneously or it needs to wait for the fix first?
You can send both maybe just mention under the --- that "this one will
generate a known kdoc warning, I'll be fixing kdoc script separately".
> > The question someone may ask, however, is whether it causes new
> > warnings to appear?
>
> I tested `make W=12 KDOCFLAGS=-Wall all` yesterday and haven't noticed
> any new issues, although expected them.
Surprising but nice.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: Kees Cook <keescook@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Alexander Duyck <alexanderduyck@fb.com>,
Yunsheng Lin <linyunsheng@huawei.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
Christoph Lameter <cl@linux.com>,
Vlastimil Babka <vbabka@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
<nex.sw.ncis.osdt.itp.upstreaming@intel.com>,
<netdev@vger.kernel.org>, <intel-wired-lan@lists.osuosl.org>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v9 7/9] libeth: add Rx buffer management
Date: Thu, 11 Apr 2024 06:45:41 -0700 [thread overview]
Message-ID: <20240411064541.7106be9a@kernel.org> (raw)
In-Reply-To: <d28896e5-32cd-4376-bb1e-44c9dbfea172@intel.com>
On Thu, 11 Apr 2024 11:07:24 +0200 Alexander Lobakin wrote:
> > I think doc tree is a strong candidate, or at least we should not
> > merge without consulting Jon. Please post and we'll figure it out.
>
> Can this series go simultaneously or it needs to wait for the fix first?
You can send both maybe just mention under the --- that "this one will
generate a known kdoc warning, I'll be fixing kdoc script separately".
> > The question someone may ask, however, is whether it causes new
> > warnings to appear?
>
> I tested `make W=12 KDOCFLAGS=-Wall all` yesterday and haven't noticed
> any new issues, although expected them.
Surprising but nice.
next prev parent reply other threads:[~2024-04-11 13:45 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 15:43 [Intel-wired-lan] [PATCH net-next v9 0/9] net: intel: start The Great Code Dedup + Page Pool for iavf Alexander Lobakin
2024-04-04 15:43 ` Alexander Lobakin
2024-04-04 15:43 ` [Intel-wired-lan] [PATCH net-next v9 1/9] net: intel: introduce {, Intel} Ethernet common library Alexander Lobakin
2024-04-04 15:43 ` [PATCH net-next v9 1/9] net: intel: introduce {,Intel} " Alexander Lobakin
2024-04-04 15:43 ` [Intel-wired-lan] [PATCH net-next v9 2/9] iavf: kill "legacy-rx" for good Alexander Lobakin
2024-04-04 15:43 ` Alexander Lobakin
2024-04-05 10:15 ` [Intel-wired-lan] " Przemek Kitszel
2024-04-05 10:15 ` Przemek Kitszel
2024-04-04 15:43 ` [Intel-wired-lan] [PATCH net-next v9 3/9] iavf: drop page splitting and recycling Alexander Lobakin
2024-04-04 15:43 ` Alexander Lobakin
2024-04-04 15:43 ` [Intel-wired-lan] [PATCH net-next v9 4/9] slab: introduce kvmalloc_array_node() and kvcalloc_node() Alexander Lobakin
2024-04-04 15:43 ` Alexander Lobakin
2024-04-05 10:12 ` [Intel-wired-lan] " Przemek Kitszel
2024-04-05 10:12 ` Przemek Kitszel
2024-04-05 10:44 ` [Intel-wired-lan] " Vlastimil Babka
2024-04-05 10:44 ` Vlastimil Babka
2024-04-04 15:43 ` [Intel-wired-lan] [PATCH net-next v9 5/9] page_pool: constify some read-only function arguments Alexander Lobakin
2024-04-04 15:43 ` Alexander Lobakin
2024-04-04 15:43 ` [Intel-wired-lan] [PATCH net-next v9 6/9] page_pool: add DMA-sync-for-CPU inline helper Alexander Lobakin
2024-04-04 15:43 ` Alexander Lobakin
2024-04-04 15:44 ` [Intel-wired-lan] [PATCH net-next v9 7/9] libeth: add Rx buffer management Alexander Lobakin
2024-04-04 15:44 ` Alexander Lobakin
2024-04-05 10:32 ` [Intel-wired-lan] " Przemek Kitszel
2024-04-05 10:32 ` Przemek Kitszel
2024-04-08 9:09 ` [Intel-wired-lan] " Alexander Lobakin
2024-04-08 9:09 ` Alexander Lobakin
2024-04-09 10:58 ` [Intel-wired-lan] " Przemek Kitszel
2024-04-09 10:58 ` Przemek Kitszel
2024-04-10 11:49 ` [Intel-wired-lan] " Alexander Lobakin
2024-04-10 11:49 ` Alexander Lobakin
2024-04-10 13:01 ` [Intel-wired-lan] " Przemek Kitszel
2024-04-10 13:01 ` Przemek Kitszel
2024-04-10 13:01 ` [Intel-wired-lan] " Alexander Lobakin
2024-04-10 13:01 ` Alexander Lobakin
2024-04-10 13:12 ` [Intel-wired-lan] " Przemek Kitszel
2024-04-10 13:12 ` Przemek Kitszel
2024-04-06 4:25 ` [Intel-wired-lan] " Jakub Kicinski
2024-04-06 4:25 ` Jakub Kicinski
2024-04-08 9:11 ` [Intel-wired-lan] " Alexander Lobakin
2024-04-08 9:11 ` Alexander Lobakin
2024-04-08 9:45 ` [Intel-wired-lan] " Alexander Lobakin
2024-04-08 9:45 ` Alexander Lobakin
2024-04-09 16:17 ` [Intel-wired-lan] " Kees Cook
2024-04-09 16:17 ` Kees Cook
2024-04-10 13:36 ` [Intel-wired-lan] " Alexander Lobakin
2024-04-10 13:36 ` Alexander Lobakin
2024-04-11 0:54 ` [Intel-wired-lan] " Jakub Kicinski
2024-04-11 0:54 ` Jakub Kicinski
2024-04-11 9:07 ` [Intel-wired-lan] " Alexander Lobakin
2024-04-11 9:07 ` Alexander Lobakin
2024-04-11 13:45 ` Jakub Kicinski [this message]
2024-04-11 13:45 ` Jakub Kicinski
2024-04-04 15:44 ` [Intel-wired-lan] [PATCH net-next v9 8/9] iavf: pack iavf_ring more efficiently Alexander Lobakin
2024-04-04 15:44 ` Alexander Lobakin
2024-04-04 15:44 ` [Intel-wired-lan] [PATCH net-next v9 9/9] iavf: switch to Page Pool Alexander Lobakin
2024-04-04 15:44 ` Alexander Lobakin
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=20240411064541.7106be9a@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aleksander.lobakin@intel.com \
--cc=alexanderduyck@fb.com \
--cc=cl@linux.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=nex.sw.ncis.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.com \
--cc=vbabka@suse.cz \
/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.