public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] logbuff: Prevent an infinite loop for console output
Date: Tue, 08 Jun 2010 16:58:06 -0500	[thread overview]
Message-ID: <1276034287.2469.19265.camel@petert> (raw)
In-Reply-To: <20100608214735.8D2D414E867@gemini.denx.de>

Hi Wolfgang,

> > I agree this fix isn't the best, but its better than the bug in my
> > opinion.  Ideally someone who uses the logbuff could provide a more
> > elegant fix.  Any takers?
> 
> I don't want to replace one bug (that bites you) with another one (
> that bites somebody else).

I think the bug that I'm introducing (continuing to use serial
output/ignoring the value of stdout) is much better than a hard lockup
(the current bug), but I definitely see your point.  I'm not a user of
the logbuff or LCDs, etc at this point in time, so feel free to do what
you'd like with the patch.

Best,
Peter

      reply	other threads:[~2010-06-08 21:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07  0:32 [U-Boot] [PATCH] logbuff: Prevent an infinite loop for console output Peter Tyser
2010-05-07  8:23 ` Detlev Zundel
2010-05-07 17:34   ` Peter Tyser
2010-06-08 21:47     ` Wolfgang Denk
2010-06-08 21:58       ` Peter Tyser [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=1276034287.2469.19265.camel@petert \
    --to=ptyser@xes-inc.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