From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/6] docs/manual: indicate how to handle BR2_TOOLCHAIN_HAS_THREADS_NPTL
Date: Thu, 13 Feb 2014 14:55:26 +0100 [thread overview]
Message-ID: <20140213145526.59af1147@skate> (raw)
In-Reply-To: <CAAXf6LWGG+8+EW9vVNMpVuYftFsOD23MmEy7ZJpBUv_3y2GMdQ@mail.gmail.com>
Dear Thomas De Schampheleire,
On Thu, 13 Feb 2014 14:46:00 +0100, Thomas De Schampheleire wrote:
> > * thread support
> > ** Dependency symbol: +BR2_TOOLCHAIN_HAS_THREADS+
> > -** Comment string: +threads+
> > +** Comment string: +threads+ (unless +BR2_TOOLCHAIN_HAS_THREADS_NPTL+
> > + is also needed, in which case, specifying only +NPTL threads+ is
> > + sufficient)
> > +
> > +* NPTL thread support
> > +** Dependency symbol: +BR2_TOOLCHAIN_HAS_THREADS_NPTL+
> > +** Comment string: +NPTL threads+
> >
> > * RPC support
> > ** Dependency symbol: +BR2_TOOLCHAIN_HAS_NATIVE_RPC+
>
> Should we maybe use 'NPTL' rather than 'NPTL threads' to make the
> string shorter? (we want to fit in 80chars).
> It's true that it's a bit more cryptic, but so is RPC, wchar, etc.
> The biggest point is that a user can go to the Toolchain menu and
> recognize a string that matches, in this case the keyword NPTL.
Fine with me. I'll adjust that in the v2, but I'll wait a little bit
more for other comments, if any :)
Thanks for the review!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-13 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 13:22 [Buildroot] [PATCH 0/6] Add toolchain knob for NPTL Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 1/6] toolchain: introduce a " Thomas Petazzoni
2014-02-17 7:11 ` Arnout Vandecappelle
2014-02-17 8:03 ` Thomas Petazzoni
2014-02-17 16:59 ` Arnout Vandecappelle
2014-02-17 22:51 ` Thomas Petazzoni
2014-02-17 22:08 ` Arnout Vandecappelle
2014-02-17 22:57 ` Thomas Petazzoni
2014-02-17 23:09 ` Arnout Vandecappelle
2014-02-13 13:22 ` [Buildroot] [PATCH 2/6] docs/manual: indicate how to handle BR2_TOOLCHAIN_HAS_THREADS_NPTL Thomas Petazzoni
2014-02-13 13:46 ` Thomas De Schampheleire
2014-02-13 13:55 ` Thomas Petazzoni [this message]
2014-02-13 13:22 ` [Buildroot] [PATCH 3/6] rt-tests: use BR2_TOOLCHAIN_HAS_THREADS_NPTL Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 4/6] sconeserver: " Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 5/6] tvheadend: " Thomas Petazzoni
2014-02-13 13:22 ` [Buildroot] [PATCH 6/6] qt5: needs NPTL threads Thomas Petazzoni
2014-02-13 13:46 ` [Buildroot] [PATCH 0/6] Add toolchain knob for NPTL Mike Zick
2014-02-18 21:06 ` Thomas Petazzoni
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=20140213145526.59af1147@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.