From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH v2 1/8] Add new FOREACH_FROM variants for queue(3)
Date: Tue, 04 Apr 2017 10:18:00 -0000 [thread overview]
Message-ID: <20170404101811.GC2961@calimero.vinschen.de> (raw)
In-Reply-To: <1491300031-6012-1-git-send-email-sebastian.huber@embedded-brains.de>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
On Apr 4 12:00, Sebastian Huber wrote:
> From: lstewart <lstewart@FreeBSD.org>
>
> Add new FOREACH_FROM variants of the queue(3) FOREACH macros which can
> optionally start the traversal from a previously found element by
> passing the element in as "var". Passing a NULL "var" retains the same
> semantics as the regular FOREACH macros.
>
> Kudos to phk for suggesting the "FROM" suffix instead of my original
> proposal.
Patchset pushed.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-04-04 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 10:00 Sebastian Huber
2017-04-04 10:00 ` [PATCH v2 3/8] Pass macro arguments properly Sebastian Huber
2017-04-04 10:00 ` [PATCH v2 6/8] queue(3): Enhance queue debugging macros Sebastian Huber
2017-04-04 10:00 ` [PATCH v2 2/8] Fix order of arguments in the TRACEBUF_INITIALIZER Sebastian Huber
2017-04-04 10:00 ` [PATCH v2 5/8] Add two new macros, SLIST_CONCAT and LIST_CONCAT Sebastian Huber
2017-04-04 10:00 ` [PATCH v2 7/8] queue.3: Document existing QMD_* macros Sebastian Huber
2017-04-04 10:00 ` [PATCH v2 4/8] Make the <sys/queue.h> fully usable within C++ Sebastian Huber
2017-04-04 10:00 ` [PATCH v2 8/8] Renumber copyright clause 4 Sebastian Huber
2017-04-04 10:18 ` Corinna Vinschen [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=20170404101811.GC2961@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@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).