public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Brian O'Dell" <brian@clarionsensing.com>
To: Dan Brown <dan.brown@nrl.navy.mil>
Cc: linux-mtd@lists.infradead.org
Subject: Re: DOCBoot doesn't compile
Date: Wed, 29 Jun 2005 16:50:56 -0500	[thread overview]
Message-ID: <42C317C0.1010803@clarionsensing.com> (raw)
In-Reply-To: <42C3009A.6020700@nrl.navy.mil>

Dan Brown wrote:

> Dan Brown wrote:
>
>> It's been a while since I've actually run DOCBoot (I've been working 
>> on other stuff), so I just built and installed it on my device from 
>> the latest CVS as a sanity check.  I get the same hard lockup as you do.
>>
>> I'll let you know when I've found the problem.  Needless to say, I'm 
>> a bit embarassed to have checked in code this broken and let it sit 
>> that way in the repository for several months :(
>
>
>
> OK, I found the issue; I was clobbering a register I shouldn't have.  
> I guess I must have made this change right before I committed the 
> latest version and not properly tested it.
>
> I'd appreciate feedback from anyone interested in using DOCBoot... 
> does the latest CVS now work for you?
>
>     -Dan
>
>
It works great.  You are my new hero man.  Thank you!  Thanks to dwmw2 
and the entire mtd team for putting all of this together for us to use.  
You guys are doing good work. 

bto

      reply	other threads:[~2005-06-29 21:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-27 18:05 DOCBoot doesn't compile Brian O'Dell
2005-06-27 18:50 ` Dan Brown
2005-06-28 16:54   ` Brian O'Dell
2005-06-28 19:12     ` Dan Brown
2005-06-28 21:39       ` Brian O'Dell
2005-06-29 18:39         ` Brian O'Dell
2005-06-29 18:47           ` Dan Brown
2005-06-29 20:12             ` Dan Brown
2005-06-29 21:50               ` Brian O'Dell [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=42C317C0.1010803@clarionsensing.com \
    --to=brian@clarionsensing.com \
    --cc=dan.brown@nrl.navy.mil \
    --cc=linux-mtd@lists.infradead.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