From: David Chow <davidchow@shaolinmicro.com>
To: linux-kernel@vger.kernel.org
Subject: serial port buffer commit
Date: Wed, 27 Nov 2002 10:24:17 +0800 [thread overview]
Message-ID: <3DE42CD1.8040902@shaolinmicro.com> (raw)
Hi all,
I am writing a kernel thread for serial port communication. If the
serial character device file is opened by a filp_open() or manipulating
using a struct file in the kernel, how can I know whether the previous
written buffer has commit or not? Similarly, how do I know is there any
data ready for read for non blocking access? Thanks.
regards,
David Chow
next reply other threads:[~2002-11-27 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 2:24 David Chow [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 15:56 serial port buffer commit David Chow
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=3DE42CD1.8040902@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=linux-kernel@vger.kernel.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