From: Greg KH <gregkh@linuxfoundation.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: chenhuacai@loongson.cn, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] LoongArch: Ensure FP/SIMD registers in the core dump file is" failed to apply to 6.4-stable tree
Date: Sun, 27 Aug 2023 10:37:58 +0200 [thread overview]
Message-ID: <2023082731-dotted-plexiglas-ce0d@gregkh> (raw)
In-Reply-To: <CAAhV-H5WYTGSvkz6tgZZud7gUOYyQGUXgSY_7ipe_0BGkz=YeQ@mail.gmail.com>
On Sun, Aug 27, 2023 at 04:23:35PM +0800, Huacai Chen wrote:
> On Sun, Aug 27, 2023 at 2:45 PM <gregkh@linuxfoundation.org> wrote:
> >
> >
> > The patch below does not apply to the 6.4-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-6.4.y
> > git checkout FETCH_HEAD
> > git cherry-pick -x 656f9aec07dba7c61d469727494a5d1b18d0bef4
> > # <resolve conflicts, build, test, etc.>
> > git commit -s
> > git send-email --to '<stable@vger.kernel.org>' --in-reply-to '2023082705-predator-enjoyable-15fb@gregkh' --subject-prefix 'PATCH 6.4.y' HEAD^..
> >
> > Possible dependencies:
> I'm sorry, this is my mistake. 6.4 also need to cut the simd_get()
> part, because simd is only supported since 6.5
I do not understand, sorry. Is this relevant for 6.4.y? If so, can you
provide a working backport?
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-27 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 6:45 FAILED: patch "[PATCH] LoongArch: Ensure FP/SIMD registers in the core dump file is" failed to apply to 6.4-stable tree gregkh
2023-08-27 8:23 ` Huacai Chen
2023-08-27 8:37 ` Greg KH [this message]
2023-08-27 8:45 ` Huacai Chen
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=2023082731-dotted-plexiglas-ce0d@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--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