From: "Arnd Bergmann" <arnd@kernel.org>
To: "Jijie Shao" <shaojijie@huawei.com>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
andrew+netdev@lunn.ch, "Simon Horman" <horms@kernel.org>
Cc: "Jian Shen" <shenjian15@huawei.com>,
liuyonglong@huawei.com, "Hao Chen" <chenhao418@huawei.com>,
"Jonathan Cameron" <jonathan.cameron@huawei.com>,
"Shameerali Kolothum Thodi"
<shameerali.kolothum.thodi@huawei.com>,
"Salil Mehta" <salil.mehta@huawei.com>,
Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 00/11] net: hns3: use seq_file for debugfs
Date: Tue, 08 Jul 2025 15:32:31 +0200 [thread overview]
Message-ID: <38355e48-8eba-4e1b-8811-969a8ec3a669@app.fastmail.com> (raw)
In-Reply-To: <20250708130029.1310872-1-shaojijie@huawei.com>
On Tue, Jul 8, 2025, at 15:00, Jijie Shao wrote:
> Arnd reported that there are two build warning for on-stasck
> buffer oversize. As Arnd's suggestion, using seq file way
> to avoid the stack buffer or kmalloc buffer allocating.
>
Thank you for cleaning this up!
Acked-by: Arnd Bergmann <arnd@arndb.de>
prev parent reply other threads:[~2025-07-08 13:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 13:00 Jijie Shao
2025-07-08 13:00 ` [PATCH net-next 01/11] net: hns3: remove tx spare info from debugfs Jijie Shao
2025-07-08 14:31 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 02/11] net: hns3: clean up the build warning in debugfs by use seq file Jijie Shao
2025-07-08 14:33 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 03/11] net: hns3: use seq_file for files in queue/ in debugfs Jijie Shao
2025-07-08 14:34 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 04/11] net: hns3: use seq_file for files in common/ of hns3 layer Jijie Shao
2025-07-08 14:36 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 05/11] net: hns3: use seq_file for files in tm/ in debugfs Jijie Shao
2025-07-08 14:38 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 06/11] net: hns3: use seq_file for files in mac_list/ " Jijie Shao
2025-07-08 14:39 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 07/11] net: hns3: use seq_file for files in reg/ " Jijie Shao
2025-07-08 14:40 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 08/11] net: hns3: use seq_file for files in fd/ " Jijie Shao
2025-07-08 14:40 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 09/11] net: hns3: use seq_file for files in common/ of hclge layer Jijie Shao
2025-07-08 14:41 ` Andrew Lunn
2025-07-11 0:39 ` Jakub Kicinski
2025-07-08 13:00 ` [PATCH net-next 10/11] net: hns3: use seq_file for files in tx_bd_info/ and rx_bd_info/ in debugfs Jijie Shao
2025-07-08 14:41 ` Andrew Lunn
2025-07-08 13:00 ` [PATCH net-next 11/11] net: hns3: remove the unused code after using seq_file Jijie Shao
2025-07-08 14:42 ` Andrew Lunn
2025-07-08 13:32 ` Arnd Bergmann [this message]
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=38355e48-8eba-4e1b-8811-969a8ec3a669@app.fastmail.com \
--to=arnd@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=chenhao418@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=salil.mehta@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shaojijie@huawei.com \
--cc=shenjian15@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®