public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Harald Freudenberger <freude@linux.ibm.com>
To: gregkh@linuxfoundation.org
Cc: dengler@linux.ibm.com, hca@linux.ibm.com, jchrist@linux.ibm.com,
	nsg@linux.ibm.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] s390/cpacf: Split and rework cpacf query functions" failed to apply to 5.10-stable tree
Date: Thu, 13 Jun 2024 13:31:40 +0200	[thread overview]
Message-ID: <32c44bf380d30f44021255c3e8369085@linux.ibm.com> (raw)
In-Reply-To: <2024061358-scanning-hacksaw-0540@gregkh>

On 2024-06-13 12:09, gregkh@linuxfoundation.org wrote:
> The patch below does not apply to the 5.10-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>.
> 
> To reproduce the conflict and resubmit, you may use the following 
> commands:
> 
> git fetch
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
> linux-5.10.y
> git checkout FETCH_HEAD
> git cherry-pick -x 830999bd7e72f4128b9dfa37090d9fa8120ce323
> # <resolve conflicts, build, test, etc.>
> git commit -s
> git send-email --to '<stable@vger.kernel.org>' --in-reply-to
> '2024061358-scanning-hacksaw-0540@gregkh' --subject-prefix 'PATCH
> 5.10.y' HEAD^..
> 
> Possible dependencies:
> 
> 830999bd7e72 ("s390/cpacf: Split and rework cpacf query functions")
> b84d0c417a5a ("s390/cpacf: get rid of register asm")
> 
> thanks,
> 
> greg k-h
> 

...

Thanks Greg, but I think we don't need this patch for this stable 
kernel.

      reply	other threads:[~2024-06-13 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 10:09 FAILED: patch "[PATCH] s390/cpacf: Split and rework cpacf query functions" failed to apply to 5.10-stable tree gregkh
2024-06-13 11:31 ` Harald Freudenberger [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=32c44bf380d30f44021255c3e8369085@linux.ibm.com \
    --to=freude@linux.ibm.com \
    --cc=dengler@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hca@linux.ibm.com \
    --cc=jchrist@linux.ibm.com \
    --cc=nsg@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox