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 07:56:25 +0200	[thread overview]
Message-ID: <20190808055625.GA24491@kroah.com> (raw)
In-Reply-To: <20190807205849.ualpzgp52crdmdol@wunner.de>

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.
> 
> That's odd, it works for me:
> 
> $ git fetch linux-stable
> $ git checkout linux-stable/linux-5.2.y
> Checking out files: 100% (43562/43562), done.
> HEAD is now at 5697a9d... Linux 5.2.7
> $ git am /tmp/pt
> Applying: spi: bcm2835: Fix 3-wire mode if DMA is enabled
> 
> Could you be a little more specific why it couldn't be applied
> when you tried it?

Sorry, that's the problem of form letters, sometimes they are wrong :(

The patch applies everywhere, but breaks the build in all trees.  So it
needs to be modified to build properly.  I need to write up a different
error message for this type of failure one of these days, luckily it is
pretty rare.

thanks,

greg k-h

  reply	other threads:[~2019-08-08  5:56 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 [this message]
2019-08-08  6:23     ` Lukas Wunner
2019-08-08 10:01       ` Greg KH

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=20190808055625.GA24491@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.