public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Joseph Myers <joseph@codesourcery.com>, libc-alpha@sourceware.org
Subject: Re: Use Linux 6.2 in build-many-glibcs.py
Date: Wed, 22 Feb 2023 17:01:13 -0300	[thread overview]
Message-ID: <9aff4b55-ff4b-2b5e-d45e-88ce80c7e589@linaro.org> (raw)
In-Reply-To: <b059bffe-a659-9f5-5613-11d6d94dde64@codesourcery.com>



On 22/02/23 15:00, Joseph Myers wrote:
> This patch makes build-many-glibcs.py use Linux 6.2.
> 
> Tested with build-many-glibcs.py (host-libraries, compilers and glibcs
> builds).


LGTM, thanks.

Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

> 
> ---
> 
> Avoiding a test failure for hppa also needs
> <https://sourceware.org/pipermail/libc-alpha/2023-February/145805.html>.
> 
> diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
> index bd212dbc82..29c10c2916 100755
> --- a/scripts/build-many-glibcs.py
> +++ b/scripts/build-many-glibcs.py
> @@ -797,7 +797,7 @@ class Context(object):
>                              'gcc': 'vcs-12',
>                              'glibc': 'vcs-mainline',
>                              'gmp': '6.2.1',
> -                            'linux': '6.1',
> +                            'linux': '6.2',
>                              'mpc': '1.3.1',
>                              'mpfr': '4.2.0',
>                              'mig': 'vcs-mainline',
> 

      reply	other threads:[~2023-02-22 20:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 18:00 Joseph Myers
2023-02-22 20:01 ` Adhemerval Zanella Netto [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=9aff4b55-ff4b-2b5e-d45e-88ce80c7e589@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).