From: Andrew Lunn <andrew@lunn.ch>
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 3/4] net: dsa: motorcomm: Dynamically allocate port structures
Date: Wed, 1 Jul 2026 00:12:56 +0200 [thread overview]
Message-ID: <83ec8bc4-5c6e-4b44-ae38-93229433daaf@lunn.ch> (raw)
In-Reply-To: <20260629183137.541341-4-mmyangfl@gmail.com>
On Tue, Jun 30, 2026 at 02:31:34AM +0800, David Yang wrote:
> With support for LED introduced later, struct yt921x_priv will be 17k
> which is not very good for a single kmalloc(). Convert the ports array
> to a array of pointers to stop bloating the priv struct.
>
> Signed-off-by: David Yang <mmyangfl@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2026-06-30 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 18:31 [PATCH net-next v2 0/4] net: dsa: motorcomm: Add LED support David Yang
2026-06-29 18:31 ` [PATCH net-next v2 1/4] net: dsa: motorcomm: Move to subdirectory David Yang
2026-06-30 22:10 ` Andrew Lunn
2026-06-29 18:31 ` [PATCH net-next v2 2/4] net: dsa: motorcomm: Split SMI module David Yang
2026-06-30 22:12 ` Andrew Lunn
2026-06-29 18:31 ` [PATCH net-next v2 3/4] net: dsa: motorcomm: Dynamically allocate port structures David Yang
2026-06-30 22:12 ` Andrew Lunn [this message]
2026-06-29 18:31 ` [PATCH net-next v2 4/4] net: dsa: motorcomm: Add LED support David Yang
2026-06-30 22:25 ` Andrew Lunn
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=83ec8bc4-5c6e-4b44-ae38-93229433daaf@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox