From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Arnd Bergmann <arnd@arndb.de>, Tony Lindgren <tony@atomide.com>,
Sekhar Nori <nsekhar@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Olof Johansson <olof@lixom.net>,
linux-omap <linux-omap@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: ti: Enable networking options for nfs boot
Date: Fri, 30 Oct 2020 11:36:24 +0200 [thread overview]
Message-ID: <497f744e-68be-7a87-6a18-824249ddcac8@ti.com> (raw)
In-Reply-To: <CAK8P3a1-CCcKmEkdw+NNr4Yo7z+BEzX0g7uU_SnXOB+VEZm8HA@mail.gmail.com>
Hi Arnd,
On 29/10/2020 22:06, Arnd Bergmann wrote:
> On Thu, Oct 29, 2020 at 8:15 PM Grygorii Strashko
> <grygorii.strashko@ti.com> wrote:
>> 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?
>
> I would prefer if a platform maintainer (I assume Tony in this case)
> picks it up and forwards it to soc@kernel.org together with other
> related changes. Olof and I tend to ignore patches sent directly
> to us, so we don't get in the way of platform maintainers that
> may have already merged similar patches or have comments.
>
> I suspect Tony didn't pick it up either because from the patch
> subject and the description, it is not clear that he is the one
> to act on it. It helps to be more specific and ask the maintainer
> by addressing them in person below the '---' line, as well as
> only putting one person in 'To:' and the rest in 'Cc:'.
Thanks for your comments and sorry that I disturbed you.
But, honestly, I'm confused (and probably I'm not the first one) as multi_v7 is common
for all ARM platforms while change is TI OMAP specific,
and neither Documentation neither get_maintainer.pl provide any reliable information
on how to proceed :( and who should be responsible for merging multi_x patches.
I'd really have tried to do some checking while preparing patch and TO/CC list - some patches applied by
platform maintainers, but some by top ARM maintainers.
>
> One comment on the contents of the patch: IIRC this is a fairly
> large driver. To ensure we don't burden other users too much,
> can you include the size of the vmlinux file before and after
> this patch?
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)
--
Best regards,
grygorii
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-10-30 9:37 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
2020-10-29 20:06 ` Arnd Bergmann
2020-10-30 9:36 ` Grygorii Strashko [this message]
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=497f744e-68be-7a87-6a18-824249ddcac8@ti.com \
--to=grygorii.strashko@ti.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--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