From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] What is the difference between /lib and /common
Date: Sat, 28 May 2011 20:51:46 +1000 [thread overview]
Message-ID: <4DE0D3C2.50004@gmail.com> (raw)
Hi Wolfgang,
A quick question for you - What defines what belongs in /lib versus /common?
I get that cmd* and env* belong in /common (U-Boot specific) and crc, zlib,
gunzip, qsort etc belong in /lib (generic)
But others are a bit grey like malloc in /common and display_options() in /lib
The reason I ask is to know where to put the new timer API - I'm thinking
/lib/time.c with udelay() makes the most sense
Regards,
Graeme
next reply other threads:[~2011-05-28 10:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 10:51 Graeme Russ [this message]
2011-05-28 14:53 ` [U-Boot] What is the difference between /lib and /common Mike Frysinger
2011-06-01 20:03 ` Wolfgang Denk
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=4DE0D3C2.50004@gmail.com \
--to=graeme.russ@gmail.com \
--cc=u-boot@lists.denx.de \
/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