All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: yangerkun <yangerkun@huawei.com>,
	sashal@kernel.org, linux-kernel@vger.kernel.org,
	chenwenyong2@huawei.com, stable@vger.kernel.org,
	"zhangyi (F)" <yi.zhang@huawei.com>
Subject: Re: Patch "spi: Fix controller unregister order" has been added to the 4.4-stable tree
Date: Sun, 6 Dec 2020 10:47:32 +0100	[thread overview]
Message-ID: <X8yotKZNLzhtxaYB@kroah.com> (raw)
In-Reply-To: <20201205174207.GA4028@wunner.de>

On Sat, Dec 05, 2020 at 06:42:07PM +0100, Lukas Wunner wrote:
> On Sat, Oct 10, 2020 at 04:41:09PM +0800, yangerkun wrote:
> > ?? 2020/6/16 9:56, Sasha Levin ????:
> > > This is a note to let you know that I've just added the patch titled
> > > 
> > >      spi: Fix controller unregister order
> > > 
> > > to the 4.4-stable tree which can be found at:
> [...]
> > > --- a/drivers/spi/spi.c
> > > +++ b/drivers/spi/spi.c
> > > @@ -1922,11 +1922,12 @@ void spi_unregister_master(struct spi_master *master)
> > >   			dev_err(&master->dev, "queue remove failed\n");
> > >   	}
> > > +	device_for_each_child(&master->dev, NULL, __unregister);
> > > +
> > 
> > This is a wrong patch. We should move this line before
> > spi_destroy_queue, but we didn't. 4.9 stable exists this
> > problem too.
> 
> Hi Sasha, Hi Greg,
> 
> below please find a patch for the 4.9-stable tree to fix the backporting
> issue reported above.

Now applied, thanks.

greg k-h

      reply	other threads:[~2020-12-06  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200616015646.AC54E2074D@mail.kernel.org>
2020-10-10  8:41 ` Patch "spi: Fix controller unregister order" has been added to the 4.4-stable tree yangerkun
2020-12-05 17:42   ` Lukas Wunner
2020-12-06  9:47     ` 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=X8yotKZNLzhtxaYB@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chenwenyong2@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.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 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.