mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Chen-Yu Tsai <wens@csie.org>,
	Support Opensource <support.opensource@diasemi.com>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-iio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev
Subject: Re: [PATCH 1/2] iio: adc: Constify struct iio_map
Date: Sun, 8 Sep 2024 13:44:33 +0200	[thread overview]
Message-ID: <eb89a77d-c733-4efd-be19-b95039ae10ee@wanadoo.fr> (raw)
In-Reply-To: <20240908114546.395661ef@jic23-huawei>

Le 08/09/2024 à 12:45, Jonathan Cameron a écrit :
> On Sat,  7 Sep 2024 19:24:46 +0200
> Christophe JAILLET <christophe.jaillet-39ZsbGIQGT5GWvitb5QawA@public.gmane.org> wrote:
> 
>> 'struct iio_map' are not modified in these drivers.
>>
>> Constifying this structure moves some data to a read-only section, so
>> increase overall security.
>>
>> In order to do it, the prototype of iio_map_array_register() and
>> devm_iio_map_array_register(), and a few structures that hold a
>> "struct iio_map *" need to be adjusted.
>>
>> On a x86_64, with allmodconfig, as an example:
>> Before:
>> ======
>>     text	   data	    bss	    dec	    hex	filename
>>    21086	    760	      0	  21846	   5556	drivers/iio/adc/axp20x_adc.o
>>
>> After:
>> =====
>>     text	   data	    bss	    dec	    hex	filename
>>    21470	    360	      0	  21830	   5546	drivers/iio/adc/axp20x_adc.o
>>    33842	   1697	    384	  35923	   8c53	drivers/iio/addac/ad74413r.o
> Cropping was a bit random, given before and after have different files.

Argh, the 2nd line related to ad74413r.o should be removed. Only the 1st 
one is relevant.

Sorry about that.

> 
> Anyhow, doesn't matter much, so applied as is.
> Note this is 6.13 material now.
> 
> Thanks,

Thanks,

CJ

> 
> Jonathan


      reply	other threads:[~2024-09-08 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-07 17:24 Christophe JAILLET
2024-09-07 17:24 ` [PATCH 2/2] iio: adc: Convert to IIO_MAP() Christophe JAILLET
2024-09-08 10:45 ` [PATCH 1/2] iio: adc: Constify struct iio_map Jonathan Cameron
2024-09-08 11:44   ` Christophe JAILLET [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=eb89a77d-c733-4efd-be19-b95039ae10ee@wanadoo.fr \
    --to=christophe.jaillet@wanadoo.fr \
    --cc=jernej.skrabec@gmail.com \
    --cc=jic23@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=samuel@sholland.org \
    --cc=support.opensource@diasemi.com \
    --cc=wens@csie.org \
    /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®