From: Sasha Levin <sashal@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: stable@kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Pablo Galindo Salgado <pablogsal@gmail.com>,
stable <stable@vger.kernel.org>
Subject: Re: 6.1-stable backport request
Date: Wed, 8 May 2024 16:18:11 -0400 [thread overview]
Message-ID: <ZjveA_YEh_N5l9o5@sashalap> (raw)
In-Reply-To: <CAM9d7cjkv9VvV=NAxdsnFKcjq1ti-cAdxFn5KkisAi-yE6Sb0Q@mail.gmail.com>
On Tue, May 07, 2024 at 04:10:50PM -0700, Namhyung Kim wrote:
>Hello,
>
>On Fri, Feb 2, 2024 at 3:29 PM Namhyung Kim <namhyung@gmail.com> wrote:
>>
>> Hello,
>>
>> Please queue up these commits for 6.1-stable:
>>
>> * commit: 4fb54994b2360ab5029ee3a959161f6fe6bbb349
>> ("perf unwind-libunwind: Fix base address for .eh_frame")
>>
>> * commit: c966d23a351a33f8a977fd7efbb6f467132f7383
>> ("perf unwind-libdw: Handle JIT-generated DSOs properly")
>>
>> They are needed to support JIT code in the perf tools.
>> I think there will be some conflicts, I will send backports soon.
>
>Have you received my backport patches? I'm wondering if
>they're missing or have other problems.
I haven't, nor do I see them on the list. Could you resend please?
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-05-08 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAM9d7cgVCqYVirivv3ApCq18eSCUuJjUoq7hbhw7X9AaTwNf+w@mail.gmail.com>
2024-05-07 23:10 ` 6.1-stable backport request Namhyung Kim
2024-05-08 20:18 ` Sasha Levin [this message]
2024-05-08 21:00 ` [PATCH for-v6.1 1/2] perf unwind-libunwind: Fix base address for .eh_frame Namhyung Kim
2024-05-08 21:00 ` [PATCH for-v6.1 2/2] perf unwind-libdw: Handle JIT-generated DSOs properly Namhyung Kim
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=ZjveA_YEh_N5l9o5@sashalap \
--to=sashal@kernel.org \
--cc=acme@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=namhyung@kernel.org \
--cc=pablogsal@gmail.com \
--cc=stable@kernel.org \
--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