linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Dmitry Osipenko <digetx@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org
Subject: Re: [PATCH v4 1/2] i2c: tegra: allow DVC support to be compiled out
Date: Mon, 5 Jun 2023 10:35:44 +0200	[thread overview]
Message-ID: <ZH2eYAIkKzbaZPff@shikoro> (raw)
In-Reply-To: <857cca81cdda30c1a2b5fb87e81cc50ec6c51e63.1683407699.git.mirq-linux@rere.qmqm.pl>

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

On Sat, May 06, 2023 at 11:19:01PM +0200, Michał Mirosław wrote:
> Save a bit of code for newer Tegra platforms by compiling out
> DVC's I2C mode support that's used only for Tegra2.
> 
> $ size i2c-tegra.o
>     text    data     bss     dec     hex filename
> -  11381     292       8   11681    2da1 i2c-tegra.o
> +  10193     292       8   10493    28fd i2c-tegra.o
> 
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
> Reviewed-by: Dmitry Osipenko <digetx@gmail.com>
> Reviewed-by: Wolfram Sang <wsa@kernel.org>
> 

Applied to for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-06-05  8:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1683407699.git.mirq-linux@rere.qmqm.pl>
2023-05-06 21:19 ` [PATCH v4 1/2] i2c: tegra: allow DVC support to be compiled out Michał Mirosław
2023-06-05  8:35   ` Wolfram Sang [this message]
2023-05-06 21:19 ` [PATCH v4 2/2] i2c: tegra: allow VI " Michał Mirosław
2023-06-05  8:35   ` Wolfram Sang

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=ZH2eYAIkKzbaZPff@shikoro \
    --to=wsa@kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).