public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Joseph Myers <josmyers@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Use Linux 6.8 in build-many-glibcs.py
Date: Tue, 12 Mar 2024 19:03:02 -0700	[thread overview]
Message-ID: <CAMe9rOoCzW3cRpE1NeN=uTo66CVsaJZ275Wk_h7xo0Ew9myuqg@mail.gmail.com> (raw)
In-Reply-To: <e99c8446-9f83-fbf6-fa58-d50cdfca0f7@redhat.com>

On Tue, Mar 12, 2024 at 3:29 PM Joseph Myers <josmyers@redhat.com> wrote:
>
> This patch makes build-many-glibcs.py use Linux 6.8.
>
> Tested with build-many-glibcs.py (host-libraries, compilers and glibcs
> builds).
>
> ---
>
> Note: I realise there's still one piece of the updates for 6.7 that I
> haven't got to (various new definitions in include/uapi/linux/tcp.h
> that should be added to sysdeps/gnu/netinet/tcp.h in glibc).
>
> diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
> index cc30dd5862..ecc743e672 100755
> --- a/scripts/build-many-glibcs.py
> +++ b/scripts/build-many-glibcs.py
> @@ -832,7 +832,7 @@ class Context(object):
>                              'gcc': 'vcs-13',
>                              'glibc': 'vcs-mainline',
>                              'gmp': '6.3.0',
> -                            'linux': '6.7',
> +                            'linux': '6.8',
>                              'mpc': '1.3.1',
>                              'mpfr': '4.2.1',
>                              'mig': 'vcs-mainline',
>
> --
> Joseph S. Myers
> josmyers@redhat.com
>

LGTM.

Reviewed-by: H.J. Lu <hjl.tools@gmail.com>

Thanks.

-- 
H.J.

      reply	other threads:[~2024-03-13  2:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 22:28 Joseph Myers
2024-03-13  2:03 ` H.J. Lu [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='CAMe9rOoCzW3cRpE1NeN=uTo66CVsaJZ275Wk_h7xo0Ew9myuqg@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=josmyers@redhat.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).