From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, joe@perches.com,
vladimir.oltean@nxp.com, petrm@nvidia.com,
linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com,
lkp@intel.com
Subject: Re: [PATCH net-next v2 1/1] net: dcb: move getapptrust to separate function
Date: Tue, 15 Nov 2022 14:40:15 +0000 [thread overview]
Message-ID: <166852321597.8656.17243417227147432834.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221114092950.2490451-1-daniel.machon@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 14 Nov 2022 10:29:50 +0100 you wrote:
> This patch fixes a frame size warning, reported by kernel test robot.
>
> >> net/dcb/dcbnl.c:1230:1: warning: the frame size of 1244 bytes is
> >> larger than 1024 bytes [-Wframe-larger-than=]
>
> The getapptrust part of dcbnl_ieee_fill is moved to a separate function,
> and the selector array is now dynamically allocated, instead of stack
> allocated.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/1] net: dcb: move getapptrust to separate function
https://git.kernel.org/netdev/net-next/c/7eba4505394e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-15 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 9:29 [PATCH net-next v2 1/1] net: dcb: move getapptrust to separate function Daniel Machon
2022-11-15 14:40 ` patchwork-bot+netdevbpf [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=166852321597.8656.17243417227147432834.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joe@perches.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vladimir.oltean@nxp.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