public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
	soc@kernel.org, Arnd Bergmann <arnd@arndb.de>,
	Sekhar Nori <nsekhar@ti.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Vignesh Raghavendra <vigneshr@ti.com>,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH v2] ARM: multi_v7_defconfig: ti: Enable networking options for nfs boot
Date: Mon, 16 Nov 2020 11:04:29 +0200	[thread overview]
Message-ID: <20201116090429.GB26857@atomide.com> (raw)
In-Reply-To: <20201030124650.20349-1-grygorii.strashko@ti.com>

* Grygorii Strashko <grygorii.strashko@ti.com> [201030 14:47]:
> Enable networking options required for NFS boot on TI platforms, which is
> widely for automated test systems.
> - enable new TI CPSW switch driver and related NET_SWITCHDEV config
> - enable TI DP83867 phy
> - explicitly enable PTP clock support to ensure dependent networking
> drivers will stay built-in.
> 
> vmlinux size changes:
> - before:
>    text       data        bss        dec        hex    filename
> 14703736    8024602     444976    23173314    16198c2    ./omap-arm/vmlinux
> 
> - after:
>    text       data        bss        dec        hex    filename
> 14727271    8029150     444528    23200949    16204b5    ./omap-arm/vmlinux
> 
> diff: 27635 (dec)

Thanks applying into omap-for-v5.11/defconfig.

Tony

  reply	other threads:[~2020-11-16  9:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 12:46 [PATCH v2] ARM: multi_v7_defconfig: ti: Enable networking options for nfs boot Grygorii Strashko
2020-11-16  9:04 ` Tony Lindgren [this message]
     [not found]   ` <CAK8P3a0-LWzSvvKkH5xVAoCfNGG_fhDJ37AZVW+qknSZU1wxDw@mail.gmail.com>
2020-11-23 17:27     ` Tony Lindgren

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=20201116090429.GB26857@atomide.com \
    --to=tony@atomide.com \
    --cc=arnd@arndb.de \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=soc@kernel.org \
    --cc=vigneshr@ti.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