From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] Update the documentation to add these changes
Date: Thu, 12 Jan 2012 09:30:08 +0100 [thread overview]
Message-ID: <20120112093008.63cf020d@skate> (raw)
In-Reply-To: <ad9fb6b99c31f84658dcc8f15cbd5c2440ee0918.1326304128.git.maxime.ripard@free-electrons.com>
Le Wed, 11 Jan 2012 18:53:41 +0100,
Maxime Ripard <maxime.ripard@free-electrons.com> a ?crit :
> +* +LIBFOO_DEVICES+ lists the device files to be created by Buildroot
> + when using the static device table. The syntax to use is the
> + makedevs one.
Would be great to mention that <foo>_DEVICES and <foo>_PERMISSIONS are
optional, and where to find the makedevs syntax, or mention it directly
in the documentation (better).
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-01-12 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 17:53 [Buildroot] [pull request v4] Pull request for branch for-2012.02/pkg-device Maxime Ripard
2012-01-11 17:53 ` [Buildroot] [PATCH 1/4] Add support for package-declared devices Maxime Ripard
2012-01-20 23:23 ` Arnout Vandecappelle
2012-01-11 17:53 ` [Buildroot] [PATCH 2/4] Convert busybox to the device declaration method Maxime Ripard
2012-01-20 23:30 ` Arnout Vandecappelle
2012-02-01 22:04 ` Peter Korsgaard
2012-01-11 17:53 ` [Buildroot] [PATCH 3/4] Migrate Xenomai to the new infrastructure Maxime Ripard
2012-01-11 17:53 ` [Buildroot] [PATCH 4/4] Update the documentation to add these changes Maxime Ripard
2012-01-12 8:30 ` Thomas Petazzoni [this message]
2012-02-01 22:08 ` Peter Korsgaard
2012-02-17 23:30 ` [Buildroot] [PATCH] Add documentation for makedev Maxime Ripard
2012-02-19 21:56 ` Peter Korsgaard
2012-02-01 22:07 ` [Buildroot] [pull request v4] Pull request for branch for-2012.02/pkg-device Peter Korsgaard
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=20120112093008.63cf020d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox