From: Scott Wood <scottwood@freescale.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linuxppc-dev@ozlabs.org, brueckner@linux.vnet.ibm.com,
Timur Tabi <timur@freescale.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hvc_console: returning 0 from put_chars is not an error
Date: Thu, 15 Oct 2009 14:32:54 -0500 [thread overview]
Message-ID: <4AD778E6.7020806@freescale.com> (raw)
In-Reply-To: <200910152126.28024.borntraeger@de.ibm.com>
Christian Borntraeger wrote:
> About the backends, there are some that spin until the text is delivered (e.g.
> virtio) , others can drop (e.g. iucv is a connection oriented protocol and it
> will (and has to) drop if there is no connection).
Sure, dropping due to not having a connection makes sense. That's
different from merely being busy. Can the iucv code tell the difference
between those two states?
-Scott
next prev parent reply other threads:[~2009-10-15 19:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 21:53 [PATCH] hvc_console: returning 0 from put_chars is not an error Timur Tabi
2009-10-15 11:05 ` Christian Borntraeger
2009-10-15 11:05 ` Christian Borntraeger
2009-10-15 16:09 ` Scott Wood
2009-10-15 16:09 ` Scott Wood
2009-10-15 18:41 ` Christian Borntraeger
2009-10-15 18:41 ` Christian Borntraeger
2009-10-15 18:55 ` Timur Tabi
2009-10-15 18:55 ` Timur Tabi
2009-10-15 18:57 ` Scott Wood
2009-10-15 18:57 ` Scott Wood
2009-10-15 19:26 ` Christian Borntraeger
2009-10-15 19:26 ` Christian Borntraeger
2009-10-15 19:32 ` Scott Wood [this message]
2009-10-16 8:49 ` Hendrik Brueckner
2009-10-16 8:49 ` Hendrik Brueckner
2009-10-17 23:17 ` Timur Tabi
2009-10-16 4:46 ` Benjamin Herrenschmidt
2009-10-16 4:46 ` Benjamin Herrenschmidt
2009-10-16 15:33 ` Scott Wood
2009-10-16 15:33 ` Scott Wood
2009-10-16 18:03 ` Benjamin Herrenschmidt
2009-10-16 18:03 ` Benjamin Herrenschmidt
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=4AD778E6.7020806@freescale.com \
--to=scottwood@freescale.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=borntraeger@de.ibm.com \
--cc=brueckner@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.