All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lukas Wunner <lukas@wunner.de>
Cc: broonie@kernel.org, kernel@martin.sperl.org, nuno.sa@analog.com,
	wahrenst@gmx.net, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] spi: bcm2835: Fix 3-wire mode if DMA is enabled" failed to apply to 5.2-stable tree
Date: Thu, 8 Aug 2019 12:01:29 +0200	[thread overview]
Message-ID: <20190808100129.GA23844@kroah.com> (raw)
In-Reply-To: <20190808062329.njfou4kfqwlz24qn@wunner.de>

On Thu, Aug 08, 2019 at 08:23:29AM +0200, Lukas Wunner wrote:
> On Thu, Aug 08, 2019 at 07:56:25AM +0200, Greg KH wrote:
> > On Wed, Aug 07, 2019 at 10:58:49PM +0200, Lukas Wunner wrote:
> > > On Wed, Aug 07, 2019 at 06:48:07PM +0200, gregkh@linuxfoundation.org wrote:
> > > > The patch below does not apply to the 5.2-stable tree.
> > 
> > The patch applies everywhere, but breaks the build in all trees.
> 
> Ugh, yes you are right, my apologies.
> 
> The reason is that v5.3 converted spi-bcm2835.c to use the
> "spi_controller" nomenclature instead of "spi_master" with
> commit 5f336ea53b6b ("spi: bcm2835: Replace spi_master by
> spi_controller").
> 
> The replacement patch below should hopefully not break the
> build.  It's the same as upstream commit 8d8bef503658,
> except one occurrence of "ctlr" is replaced by "master".

Thanks for this, now queued up.

greg k-h

      reply	other threads:[~2019-08-08 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 16:48 FAILED: patch "[PATCH] spi: bcm2835: Fix 3-wire mode if DMA is enabled" failed to apply to 5.2-stable tree gregkh
2019-08-07 20:58 ` Lukas Wunner
2019-08-08  5:56   ` Greg KH
2019-08-08  6:23     ` Lukas Wunner
2019-08-08 10:01       ` 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=20190808100129.GA23844@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=kernel@martin.sperl.org \
    --cc=lukas@wunner.de \
    --cc=nuno.sa@analog.com \
    --cc=stable@vger.kernel.org \
    --cc=wahrenst@gmx.net \
    /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.