From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RFC: Makefile style question with testing?
Date: Mon, 26 Nov 2007 12:05:24 -0500 [thread overview]
Message-ID: <474AFCD4.4010701@ge.com> (raw)
In-Reply-To: <fa686aa40711260859m405dee5k7a25be059fd05033@mail.gmail.com>
Grant Likely wrote:
> On 11/26/07, Kumar Gala <galak@kernel.crashing.org> wrote:
>> With Grant's work in testing I was wondering of the two options I have
>> below which is preferred:
>>
>> option 1: duplicating CONFIG_OF_LIBFDT to maintain one line per source
>> file
>> option 2: put files that use same CONFIG_ on the same line
>
> option 2 happens to be my preference as long as the lines don't get
> too long or unreadable; but I don't think it's a big deal either way.
>
> g.
Ditto.
gvb
prev parent reply other threads:[~2007-11-26 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 16:48 [U-Boot-Users] RFC: Makefile style question with testing? Kumar Gala
2007-11-26 16:59 ` Grant Likely
2007-11-26 17:05 ` Jerry Van Baren [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=474AFCD4.4010701@ge.com \
--to=gerald.vanbaren@ge.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