[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <HE1PR0402MB2700B5484AAEE6F1E5799DEE94A80@HE1PR0402MB2700.eurprd04.prod.outlook.com>
Date: Fri, 23 Mar 2018 15:03:29 +0000
From: Ruxandra Ioana Ciocoi Radulescu <ruxandra.radulescu@....com>
To: Greg KH <gregkh@...uxfoundation.org>
CC: "devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/9] staging: fsl-dpaa2/eth: Move print message
> -----Original Message-----
> From: Greg KH [mailto:gregkh@...uxfoundation.org]
> Sent: Friday, March 23, 2018 5:01 PM
> To: Ruxandra Ioana Ciocoi Radulescu <ruxandra.radulescu@....com>
> Cc: devel@...verdev.osuosl.org; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH 2/9] staging: fsl-dpaa2/eth: Move print message
>
> On Fri, Mar 23, 2018 at 08:44:06AM -0500, Ioana Radulescu wrote:
> > Let the driver remove() function print an informative message
> > after it finishes removing the network interface, not at an
> > arbitrary point during cleanup.
> >
> > Signed-off-by: Ioana Radulescu <ruxandra.radulescu@....com>
> > ---
> > drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
> b/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
> > index beb5959..9fb88f2 100644
> > --- a/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
> > +++ b/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
> > @@ -2550,7 +2550,6 @@ static int dpaa2_eth_remove(struct
> fsl_mc_device *ls_dev)
> > priv = netdev_priv(net_dev);
> >
> > unregister_netdev(net_dev);
> > - dev_info(net_dev->dev.parent, "Removed interface %s\n",
> net_dev->name);
> >
> > if (priv->do_link_poll)
> > kthread_stop(priv->poll_thread);
> > @@ -2571,6 +2570,8 @@ static int dpaa2_eth_remove(struct
> fsl_mc_device *ls_dev)
> > dev_set_drvdata(dev, NULL);
> > free_netdev(net_dev);
> >
> > + dev_info(net_dev->dev.parent, "Removed interface %s\n",
> net_dev->name);
>
> Why is this even needed? I'll take it but spamming kernel logs for no
> reason is not a good idea :)
Fair point, should I make it dev_dbg instead?
Thanks,
Ioana
Powered by blists - more mailing lists