From: Murali Krishna Policharla <murali.policharla@broadcom.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: davem@davemloft.net, amritha.nambiar@intel.com,
ecree@solarflare.com, ktkhai@virtuozzo.com,
alexander.h.duyck@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: [PATCH] net: core: Fix to store new mtu setting in netdevice.
Date: Tue, 1 Jan 2019 15:18:51 +0530 [thread overview]
Message-ID: <30ecb54251911d28c50b61299b0f8d3d@mail.gmail.com> (raw)
In-Reply-To: <20190101083450.GA17613@lunn.ch>
Hi Andrew,
Currently net/dsa/slave.c does not have
ndo_change_mtu function. But shortly I will be submitting a separate
patch outside this fix that has ndo_change_mtu function support added to
DSA switch. As part of testing the newly added ndo_change_mtu function
for DSA switch it uncovered that new mtu size is not being updated to
netdevice structure. This patch fixes this issue and updates new mtu size
to netdevice structure.
Hope this clarifies, let me know if you need any further information.
Regards
Murali
-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: Tuesday, January 1, 2019 2:05 PM
To: Murali Krishna Policharla
Cc: davem@davemloft.net; amritha.nambiar@intel.com; ecree@solarflare.com;
ktkhai@virtuozzo.com; alexander.h.duyck@intel.com; netdev@vger.kernel.org;
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: core: Fix to store new mtu setting in netdevice.
On Tue, Jan 01, 2019 at 12:12:14PM +0530, Murali Krishna Policharla wrote:
> Store newly configured mtu settings in the netdevice after mtu
> configuration is successful to the dsa switch.
Hi Murali
Please could you give more details. net/dsa/slave.c does not have a
ndo_change_mtu function, so i don't know what you mean by the
reference to DSA.
Thanks
Andrew
next prev parent reply other threads:[~2019-01-01 9:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 6:42 [PATCH] net: core: Fix to store new mtu setting in netdevice Murali Krishna Policharla
2019-01-01 7:54 ` Kirill Tkhai
2019-01-01 9:40 ` Heiner Kallweit
2019-01-01 23:36 ` Andrew Lunn
2019-01-02 6:27 ` Heiner Kallweit
2019-01-01 8:34 ` Andrew Lunn
2019-01-01 9:48 ` Murali Krishna Policharla [this message]
2019-01-01 23:24 ` Andrew Lunn
2019-01-02 9:54 ` Murali Krishna Policharla
2019-01-02 13:16 ` Andrew Lunn
2019-01-03 9:54 ` Murali Krishna Policharla
2019-01-01 9:35 ` Heiner Kallweit
2019-01-01 21:44 ` David Miller
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=30ecb54251911d28c50b61299b0f8d3d@mail.gmail.com \
--to=murali.policharla@broadcom.com \
--cc=alexander.h.duyck@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).