public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: "Miguel Martín" <mmartinv@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
	Miguel Martin via Libc-stable <libc-stable@sourceware.org>
Subject: Re: [COMMITTED 2.34 0/2] Improve aligned_alloc and calloc test coverage
Date: Tue, 21 May 2024 14:51:33 +0200	[thread overview]
Message-ID: <bd73b615a725b70ca76244447ec646b2a4766d34.camel@redhat.com> (raw)
In-Reply-To: <87v8375ttx.fsf@oldenburg.str.redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, 2024-05-21 at 12:43 +0200, Florian Weimer wrote:
> * Miguel Martin via Libc-stable:
> 
> > From: Miguel Martín <mmartinv@redhat.com>
> > 
> > Backports to improve aligned_alloc and calloc test coverage in
> > glibc 2.34:
> > 
> > DJ Delorie (1):
> >   aligned_alloc: conform to C17
> > 
> > Joe Simmons-Talbott (1):
> >   malloc: Improve aligned_alloc and calloc test coverage.
> 
> As far as I can see, none of these patches have actually been
> committed
> (pushed to the official repository).
> 
> Thanks,
> Florian
> 

After talking to Arjun I think I know what you actually mean and the
answer is no, none of them have been pushed to the upstream repos, the
subject prefix should be PATCH, not COMMITTED. Sorry for the confusion.

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEERBNxlsW9fRmqDQAeOZwMQZdKxwAFAmZMmNUACgkQOZwMQZdK
xwAqIRAA3rVYQTnHa1vld0Zcz4AsMyTJIy5BZX16yvqWt5vIdw+L9Vfg38XJJldT
3hgkeJ8dVZcyWXiDvquR00KieYagSm10PXOcCX38TmFPHHyOivI5icxaLDbb5ph/
u9xzq0jAgIIe5B5xO2nEFKPYKoK0APH5Kjk4orzJS+YY47ZXQgFDTNwVVF5yLZBa
NvCg40ruNPI3Zz5MPtDQu3KUEiYsxbezf5SyrvQeuCEs71YCh7PCmUboGOcxExJ4
NYvdxdGPqyxOQ36SpiN24fANThjXkuCdvYo9q95kfbkwmm60iV2sH8wvoVtSaZx6
pNDjTkvjMkpZkXPytrZGS78lhSv1YntWNimidKUmKw9zOU9nnOzD3YXnDI8eDx+b
5GUaG4BsgK9STX4Dd5KbQJzMdOKE4kf36xxQ8nO7zATKUei2EHgjnIf7C7E97amG
mUiScQVEC5i6eOa5bBxLU1wjK39wXh8RRt01xKrj538BRFagGNsbAhF+kI9DMH3e
mZl67npQ3U+8xn99bAcAM+M5XQNBdF/6EF2WDpgry+qUj81G+eixpbq9fAOtloAd
VxCdridJ1Yh4TNNBBSGKMjNXHDmAQRRTViwCwJu9jG/RHCkhNLRVxumv4rz5GLcV
mXEhYPpWcqeaKmrWe+FUrmPw6DYm8NcdHr1x2P/pBvP3QhbXifw=
=XGlw
-----END PGP SIGNATURE-----


      parent reply	other threads:[~2024-05-21 12:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21  8:38 Miguel Martin
2024-05-21  8:38 ` [COMMITTED 2.34 1/2] aligned_alloc: conform to C17 Miguel Martin
2024-05-21  8:38 ` [COMMITTED 2.34 2/2] malloc: Improve aligned_alloc and calloc test coverage Miguel Martin
2024-05-21 10:42   ` Florian Weimer
2024-05-21 13:00     ` Miguel Martín
2024-05-21 13:06       ` Adhemerval Zanella Netto
2024-05-21 13:30         ` Miguel Martín
2024-05-21 13:32         ` Sam James
2024-05-21 13:24       ` Florian Weimer
2024-05-21 10:43 ` [COMMITTED 2.34 0/2] " Florian Weimer
2024-05-21 12:12   ` Miguel Martín
2024-05-21 12:51   ` Miguel Martín [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=bd73b615a725b70ca76244447ec646b2a4766d34.camel@redhat.com \
    --to=mmartinv@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-stable@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).