From: Scott Wood <scottwood@freescale.com>
To: Scott Wood <scottwood@freescale.com>,
jdl@jdl.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 3/3] Return a non-zero exit code if an error occurs during dts parsing.
Date: Thu, 10 Jan 2008 11:22:52 -0600 [thread overview]
Message-ID: <4786546C.7070700@freescale.com> (raw)
In-Reply-To: <20080110035609.GL17816@localhost.localdomain>
David Gibson wrote:
> On Sun, Jan 06, 2008 at 04:55:09PM -0600, Scott Wood wrote:
>> On Fri, Jan 04, 2008 at 03:30:33PM +1100, David Gibson wrote:
>>> This is unequivocally wrong. boot_info should have information about
>>> the contents of the blob, not state information like the error.
>> "This blob is invalid" *is* information about the contents of the blob.
>>
>>> If you're going to use an ugly global, then use it everywhere.
>> Why go out of our way to make the code even less library-able/thread-safe?
>
> It doesn't make it any less thread-safe. A global variable used some
> places is just as bad as a global variable used everywhere from that
> point of view, and is more complicated.
But the knowledge of the fact that the boot_info struct is a global is
isolated to the treesource code. I don't see any reason to add another
global at the *interface* level, much less that not doing so is
"unequivocally wrong".
-Scott
prev parent reply other threads:[~2008-01-10 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 23:43 [PATCH 3/3] Return a non-zero exit code if an error occurs during dts parsing Scott Wood
2008-01-04 4:30 ` David Gibson
2008-01-06 22:55 ` Scott Wood
2008-01-10 3:56 ` David Gibson
2008-01-10 17:22 ` Scott Wood [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=4786546C.7070700@freescale.com \
--to=scottwood@freescale.com \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).