All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jiri Slaby <jslaby@suse.cz>
Cc: David Miller <davem@davemloft.net>,
	stable@vger.kernel.org, madalin.bucur@nxp.com
Subject: Re: dpaa_eth bad stable backport [was: [PATCHES] Networking]
Date: Tue, 10 Jul 2018 16:03:35 +0200	[thread overview]
Message-ID: <20180710140335.GJ1123@kroah.com> (raw)
In-Reply-To: <32445611-cc59-2f30-1708-e1c8ade6171a@suse.cz>

On Thu, Jun 28, 2018 at 04:24:24PM +0200, Jiri Slaby wrote:
> On 03/28/2018, 05:35 PM, David Miller wrote:
> > Please queue up the following networking bug fixes for v4.14 and v4.15
> > -stable, respecetively.
> 
> Hi,
> 
> I wonder if this commit from this batch is correct in 4.14 and 4.15:
> commit 5bbb99d2fde047df596379be6c58e265e2ddbe1f
> Author: Madalin Bucur <madalin.bucur@nxp.com>
> Date:   Wed Mar 14 08:37:29 2018 -0500
> 
>     dpaa_eth: fix error in dpaa_remove()
> 
>     [ Upstream commit 88075256ee817041d68c2387f29065b5cb2b342a ]
> 
> 
> 
> In 4.14 and 4.15, the drvdata are set like this:
>         dev = &pdev->dev;
> …
>         dev_set_drvdata(dev, net_dev);
> 
> Opposing to 4.16:
>         dev = pdev->dev.parent;
> …
>         dev_set_drvdata(dev, net_dev);
> 
> 
> 
> 
> So the change in dpaa_remove done by the commit above is wrong IMO:
> -       dev = &pdev->dev;
> +       dev = pdev->dev.parent;
>         net_dev = dev_get_drvdata(dev);
> 
> 
> 
> Hence this should be reverted from 4.14-LTS. I think 4.15 is dead.

Now reverted, thanks.

greg k-h

      parent reply	other threads:[~2018-07-10 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 15:35 [PATCHES] Networking David Miller
2018-03-28 15:40 ` Willy Tarreau
2018-03-28 15:46   ` David Miller
2018-03-28 16:36     ` Greg KH
2018-03-28 16:49 ` Greg KH
2018-06-28 14:24 ` dpaa_eth bad stable backport [was: [PATCHES] Networking] Jiri Slaby
2018-06-29 12:30   ` Madalin-cristian Bucur
2018-07-10 14:03   ` Greg KH [this message]

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=20180710140335.GJ1123@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=jslaby@suse.cz \
    --cc=madalin.bucur@nxp.com \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.