All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Csókás Bence" <csokas.bence@prolan.hu>
Cc: broonie@kernel.org, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] spi: atmel-qspi: Memory barriers after memory-mapped I/O" failed to apply to 6.13-stable tree
Date: Tue, 11 Feb 2025 11:28:56 +0100	[thread overview]
Message-ID: <2025021128-recognize-hardhead-67f0@gregkh> (raw)
In-Reply-To: <fde3442f-3ea5-4742-af70-9d243678e303@prolan.hu>

On Mon, Feb 10, 2025 at 07:17:54PM +0100, Csókás Bence wrote:
> Hi,
> 
> On 2025. 02. 10. 13:52, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 6.13-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> 
> There is a dependency, that I specified in the commit in accordance with
> [1]:
> 
> > Cc: stable@vger.kernel.org # c0a0203cf579: ("spi: atmel-quadspi: Create `atmel_qspi_ops`"...)
> > Cc: stable@vger.kernel.org # 6.x.y
> > Signed-off-by: Bence Csókás <csokas.bence@prolan.hu>
> > Link: https://patch.msgid.link/20241219091258.395187-1-csokas.bence@prolan.hu
> > Signed-off-by: Mark Brown <broonie@kernel.org>
> 
> [1] https://docs.kernel.org/process/stable-kernel-rules.html#option-1

Sorry, I missed that.

> Please re-pick with c0a0203cf579. As a side note, I also specified 6.x.y
> because - in my experience - anything earlier will not cleanly apply
> anyways. So you can safely drop these from the 5.x.y queues.

It failed to apply to 6.1.y as well, please provide backports for that
tree if you want it there.

thanks,

greg k-h

      reply	other threads:[~2025-02-11 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 12:52 FAILED: patch "[PATCH] spi: atmel-qspi: Memory barriers after memory-mapped I/O" failed to apply to 6.13-stable tree gregkh
2025-02-10 18:17 ` Csókás Bence
2025-02-11 10:28   ` 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=2025021128-recognize-hardhead-67f0@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=csokas.bence@prolan.hu \
    --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.