linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Nishanth Menon <nm@ti.com>, Tony Lindgren <tony@atomide.com>,
	Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: <linux-omap@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, Sekhar Nori <nsekhar@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Russell King <linux@armlinux.org.uk>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: ti: Enable networking options for nfs boot
Date: Thu, 29 Oct 2020 21:15:18 +0200	[thread overview]
Message-ID: <bb6e0bd9-a8fe-f63b-14fd-92a1f8cea0bb@ti.com> (raw)
In-Reply-To: <20201002125000.5b5kho4e5de7jjrj@akan>

Hi All,

On 02/10/2020 15:50, Nishanth Menon wrote:
> On 23:27-20201001, Grygorii Strashko wrote:
>> 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
>>
>> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
>> ---
>>   arch/arm/configs/multi_v7_defconfig | 5 +++++
>>   1 file changed, 5 insertions(+)
>>
> 
> [...]
> 
> Reviewed-by: Nishanth Menon <nm@ti.com>
> 

Are there any actions need to be done to have this patch merged?

-- 
Best regards,
grygorii

  reply	other threads:[~2020-10-29 19:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 20:27 [PATCH] ARM: multi_v7_defconfig: ti: Enable networking options for nfs boot Grygorii Strashko
2020-10-02 12:50 ` Nishanth Menon
2020-10-29 19:15   ` Grygorii Strashko [this message]
2020-10-29 20:06     ` Arnd Bergmann
2020-10-30  9:36       ` Grygorii Strashko
2020-10-30 10:01         ` Arnd Bergmann

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=bb6e0bd9-a8fe-f63b-14fd-92a1f8cea0bb@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=nm@ti.com \
    --cc=nsekhar@ti.com \
    --cc=olof@lixom.net \
    --cc=tony@atomide.com \
    --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;
as well as URLs for NNTP newsgroup(s).