From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] docs/manual: enhance doc for BR2_TOOLCHAIN_HEADERS_AT_LEAST_X_Y
Date: Sun, 27 Jul 2014 15:04:07 +0200 [thread overview]
Message-ID: <20140727150407.2c81486e@free-electrons.com> (raw)
In-Reply-To: <20140727124900.GA3895@free.fr>
Dear Yann E. MORIN,
On Sun, 27 Jul 2014 14:49:00 +0200, Yann E. MORIN wrote:
> > Therefore, I'm tempted to say no to this patch, but I'm interested to
> > be convince otherwise :)
>
> Well, APIs can get deprecated over time, and eventually removed. For
> example, the status of interfaces is described in Documentation/ABI in
> your favourite kernel source tree.
Yeah, well, that's true. Even though that tends to happen very rarely
and generally for very rarely used interfaces.
> So, yes, I still think this patch is valid.
Ok, fair enough :)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-27 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 21:28 [Buildroot] [PATCH 0/2] gst-fsl-plugins: requires kernel headers <= 3.10 (branch yem/quickies) Yann E. MORIN
2014-07-25 21:28 ` [Buildroot] [PATCH 1/2] docs/manual: enhance doc for BR2_TOOLCHAIN_HEADERS_AT_LEAST_X_Y Yann E. MORIN
2014-07-26 18:25 ` Thomas De Schampheleire
2014-07-27 12:34 ` Thomas Petazzoni
2014-07-27 12:49 ` Yann E. MORIN
2014-07-27 13:04 ` Thomas Petazzoni [this message]
2014-07-27 13:08 ` Thomas Petazzoni
2014-07-25 21:28 ` [Buildroot] [PATCH 2/2] package/gst-fsl-plugins: not available for kernel headers >= 3.11 Yann E. MORIN
2014-07-25 22:32 ` [Buildroot] [PATCH 0/2] gst-fsl-plugins: requires kernel headers <= 3.10 (branch yem/quickies) Thomas Petazzoni
2014-07-25 23:21 ` Gary Bisson
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=20140727150407.2c81486e@free-electrons.com \
--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.