From: Alejandro Colomar <alx@kernel.org>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: linux-man@vger.kernel.org
Subject: Re: aligned_alloc man page and restrictions on alignment values
Date: Thu, 5 Feb 2026 15:04:20 +0100 [thread overview]
Message-ID: <aYSi4mKh8jbYy4HD@devuan> (raw)
In-Reply-To: <CACb0b4mDZx9YrpFDCmoSHvjvZpHaHMsauwzcBR-JYib0467hUw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Hi Jonathan,
On 2026-02-05T13:55:47+0000, Jonathan Wakely wrote:
> On Thu, 5 Feb 2026 at 13:26, Alejandro Colomar <alx@kernel.org> wrote:
> >
> > Hi Jonathan,
> >
> > On 2026-02-05T10:05:08+0000, Jonathan Wakely wrote:
> > > Hi,
> > >
> > > I don't understand what "except for the added restriction" means in
> > > aligned_alloc(3) here:
> > >
> > > The obsolete function memalign() allocates size bytes and returns a
> > > pointer to the allocated memory. The memory address will be a multiple
> > > of alignment, which must be a power of two.
> > >
> > > aligned_alloc() is the same as memalign(), except for the added restric‐
> > > tion that alignment must be a power of two.
> >
> > That was fixed (removed) in
>
> Oh great, thanks! I was only looking at the Fedora man-pages, I should
> have checked git first.
No problems at all!
I believe asking can sometimes be more efficient than checking, and it
triggers discussion, which may sometimes uncover unresolved issues.
So thanks for asking! :-)
Cheers,
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-05 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 10:05 aligned_alloc man page and restrictions on alignment values Jonathan Wakely
2026-02-05 13:17 ` Alejandro Colomar
2026-02-05 13:26 ` Alejandro Colomar
2026-02-05 13:55 ` Jonathan Wakely
2026-02-05 14:04 ` Alejandro Colomar [this message]
2026-02-05 15:23 ` Carlos O'Donell
2026-02-05 15:53 ` Alejandro Colomar
2026-02-06 14:09 ` Carlos O'Donell
2026-02-06 14:14 ` Alejandro Colomar
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=aYSi4mKh8jbYy4HD@devuan \
--to=alx@kernel.org \
--cc=jwakely@redhat.com \
--cc=linux-man@vger.kernel.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