From: DJ Delorie <dj@redhat.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] malloc: Remove bin scanning from memalign (bug 30723)
Date: Fri, 11 Aug 2023 19:14:08 -0400 [thread overview]
Message-ID: <xnv8dlnpdr.fsf@greed.delorie.com> (raw)
In-Reply-To: <87jzu2xcxd.fsf@oldenburg.str.redhat.com> (message from Florian Weimer on Fri, 11 Aug 2023 09:20:46 +0200)
Florian Weimer <fweimer@redhat.com> writes:
>> So yeah, I guess reverting this part of it makes sense.
>
> Should I commit both patches then?
Yes please.
next prev parent reply other threads:[~2023-08-11 23:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 17:36 Florian Weimer
2023-08-10 18:04 ` DJ Delorie
2023-08-11 7:20 ` Florian Weimer
2023-08-11 23:14 ` DJ Delorie [this message]
2023-08-21 14:01 ` Sam James
2023-08-21 14:45 ` Florian Weimer
2023-08-11 8:54 ` Maxim Kuvyrkov
2023-08-11 9:14 ` Florian Weimer
2023-08-11 14:52 ` Florian Weimer
2023-08-12 6:52 ` Andreas Schwab
2023-08-12 13:23 ` Florian Weimer
2023-08-12 13:33 ` Florian Weimer
2023-08-12 14:50 ` Andreas Schwab
2023-08-14 2:14 ` Xi Ruoyao
2023-08-14 9:16 ` Florian Weimer
2023-08-15 11:58 ` Adhemerval Zanella Netto
2023-08-14 9:42 Florian Weimer
2023-08-14 20:49 ` DJ Delorie
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=xnv8dlnpdr.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=fweimer@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).