From: chrubis@suse.cz
To: Mike Frysinger <vapier@gentoo.org>
Cc: Alexey Kodanev <alexey.kodanev@oracle.com>,
ltp-list@lists.sourceforge.net, vasily.isaenko@oracle.com
Subject: Re: [LTP] [PATCH v6] fw_load: new test of device firmware loading
Date: Wed, 3 Jul 2013 13:08:15 +0200 [thread overview]
Message-ID: <20130703110815.GA2993@rei> (raw)
In-Reply-To: <201307021650.56483.vapier@gentoo.org>
Hi!
> generally it's preferable to organize the code such that forward decls aren't
> even necessary. seems like it'd be trivial to reorganize this file as such.
I keep telling that to people yet they are stubborn to organize the
files more to the actual code flow, i.e. main() first then all the
functions uses in main and so forth...
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-07-03 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 11:43 [LTP] [PATCH v6] fw_load: new test of device firmware loading Alexey Kodanev
2013-07-02 18:24 ` chrubis
2013-07-02 20:50 ` Mike Frysinger
2013-07-03 8:02 ` alexey.kodanev
2013-07-03 10:33 ` chrubis
[not found] ` <201307031300.00679.vapier@gentoo.org>
[not found] ` <51D548FC.9010003@oracle.com>
2013-07-10 11:14 ` chrubis
[not found] ` <51DBCD1E.3040303@oracle.com>
2013-07-10 11:43 ` chrubis
2013-07-03 11:08 ` chrubis [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=20130703110815.GA2993@rei \
--to=chrubis@suse.cz \
--cc=alexey.kodanev@oracle.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=vapier@gentoo.org \
--cc=vasily.isaenko@oracle.com \
/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