[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <434070244.1141414.1557385064484@webmail.strato.com>
Date: Thu, 9 May 2019 08:57:44 +0200 (CEST)
From: Ulrich Hecht <uli@...nd.eu>
To: Niklas Söderlund <niklas.soderlund@...natech.se>,
Sergei Shtylyov <sergei.shtylyov@...entembedded.com>
Cc: Ulrich Hecht <uli+renesas@...nd.eu>,
linux-renesas-soc@...r.kernel.org, netdev@...r.kernel.org,
davem@...emloft.net, wsa@...-dreams.de, horms@...ge.net.au,
magnus.damm@...il.com
Subject: Re: [PATCH] ravb: implement MTU change while device is up
> On May 8, 2019 at 6:52 PM Niklas Söderlund <niklas.soderlund@...natech.se> wrote:
>
>
> Hi Sergei,
>
> On 2019-05-08 18:59:01 +0300, Sergei Shtylyov wrote:
> > Hello!
> >
> > On 05/08/2019 06:21 PM, Ulrich Hecht wrote:
> >
> > > Uses the same method as various other drivers: shut the device down,
> > > change the MTU, then bring it back up again.
> > >
> > > Tested on Renesas D3 Draak board.
> > >
> > > Signed-off-by: Ulrich Hecht <uli+renesas@...nd.eu>
> >
> > You should have CC'ed me (as an reviewer for the Renesas drivers).
Sorry, will do next time.
> >
> > How about the code below instead?
> >
> > if (netif_running(ndev))
> > ravb_close(ndev);
> >
> > ndev->mtu = new_mtu;
> > netdev_update_features(ndev);
>
> Is there a need to call netdev_update_features() even if the if is not
> running?
In my testing, it didn't seem so.
CU
Uli
Powered by blists - more mailing lists