mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Link Mauve <linkmauve@linkmauve.fr>
To: Link Mauve <linkmauve@linkmauve.fr>
Cc: linux-media@vger.kernel.org,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Hans Verkuil" <hverkuil+cisco@kernel.org>,
	"Bradford Love" <brad@nextdimension.cc>,
	"Kees Cook" <kees@kernel.org>,
	"Uwe Kleine-König (The Capable Hub)"
	<u.kleine-koenig@baylibre.com>,
	"Deepanshu Kartikey" <kartikey406@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Remove regmap_config struct from allocated data
Date: Sun, 20 Sep 2026 18:31:49 +0200	[thread overview]
Message-ID: <arAKdVU9CVeNMu-c@desktop> (raw)
In-Reply-To: <20260804114625.2314430-1-linkmauve@linkmauve.fr>

Hi,

Is there any interest in this series?  I know it doesn’t improve much,
but it should be easy enough to review.

On Tue, Aug 04, 2026 at 01:46:20PM +0200, Link Mauve wrote:
> This is a follow-up for eeafd9e12144fb6249e1510f9db8a4aaf8155a0a, after
> which I found a bunch of regmap_config structs defined inside of other
> structs, even though they either completely static (in which case I put
> them in .rodata), or needed only a single dynamic argument (in which
> case I put them on the stack of the function using it).
> 
> I found only these three instances in the media subsystem, which removes
> 192 bytes from the allocation of each of these driver instances.
> 
> Link Mauve (3):
>   media: rtl2832: make regmap_config static const
>   media: m88ds3103: make regmap_config static const
>   media: ts2020: put regmap_config on the stack
> 
>  drivers/media/dvb-frontends/m88ds3103.c      |  9 +++++----
>  drivers/media/dvb-frontends/m88ds3103_priv.h |  1 -
>  drivers/media/dvb-frontends/rtl2832.c        | 18 ++++++++++--------
>  drivers/media/dvb-frontends/rtl2832_priv.h   |  1 -
>  drivers/media/dvb-frontends/ts2020.c         | 15 ++++++++-------
>  5 files changed, 23 insertions(+), 21 deletions(-)
> 
> 
> base-commit: 9a4cdc958dd79fc6c3b20b51a10debec6ca09fec
> -- 
> 2.55.0
> 

-- 
Link Mauve

      parent reply	other threads:[~2026-09-20 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04 11:46 Link Mauve
2026-08-04 11:46 ` [PATCH 1/3] media: rtl2832: make regmap_config static const Link Mauve
2026-08-04 11:46 ` [PATCH 2/3] media: m88ds3103: " Link Mauve
2026-08-04 11:46 ` [PATCH 3/3] media: ts2020: put regmap_config on the stack Link Mauve
2026-09-20 19:46   ` Uwe Kleine-König
2026-09-21 17:00     ` Link Mauve
2026-09-21 18:45       ` Uwe Kleine-König
2026-09-20 16:31 ` Link Mauve [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=arAKdVU9CVeNMu-c@desktop \
    --to=linkmauve@linkmauve.fr \
    --cc=brad@nextdimension.cc \
    --cc=hverkuil+cisco@kernel.org \
    --cc=kartikey406@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=u.kleine-koenig@baylibre.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®