public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Krebbel <krebbel@linux.ibm.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH gcc-11 0/2] Backport kpatch changes
Date: Thu, 30 Sep 2021 16:14:15 +0200	[thread overview]
Message-ID: <9c85a9bd-6c3e-55af-f893-b51b83b958e0@linux.ibm.com> (raw)
In-Reply-To: <20210930085044.358172-1-iii@linux.ibm.com>

On 9/30/21 10:50, Ilya Leoshkevich wrote:
> Hi,
> 
> This series contains a backport of kpatch changes needed to support
> https://github.com/dynup/kpatch/pull/1203 so that it could be used in
> RHEL 9.  The patches have been in master for 4 months now without
> issues.
> 
> Bootstrapped and regtested on s390x-redhat-linux.
> 
> Ok for gcc-11?

Ok for both. Thanks!

Andreas

      parent reply	other threads:[~2021-09-30 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  8:50 Ilya Leoshkevich
2021-09-30  8:50 ` [PATCH gcc-11 1/2] IBM Z: Define NO_PROFILE_COUNTERS Ilya Leoshkevich
2021-09-30  8:50 ` [PATCH gcc-11 2/2] IBM Z: Use @PLT symbols for local functions in 64-bit mode Ilya Leoshkevich
2021-09-30 14:14 ` Andreas Krebbel [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=9c85a9bd-6c3e-55af-f893-b51b83b958e0@linux.ibm.com \
    --to=krebbel@linux.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iii@linux.ibm.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).