From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Engraf <david.engraf@sysgo.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: serio - add writing multiple bytes at once
Date: Mon, 30 Apr 2018 14:20:07 -0700 [thread overview]
Message-ID: <20180430212007.GC54182@dtor-ws> (raw)
In-Reply-To: <20180430090324.30845-1-david.engraf@sysgo.com>
Hi David,
On Mon, Apr 30, 2018 at 11:03:24AM +0200, David Engraf wrote:
> The current version only supports forwarding a single byte to the tty
> layer.
>
> This patch adds serio_write_length() to allow a serport driver writing
> multiple bytes at once. The patch also includes a fallback to
> serio_write_length() when a driver did not register a single byte function.
Without users I do not see point for this API.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2018-04-30 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 9:03 [PATCH] Input: serio - add writing multiple bytes at once David Engraf
2018-04-30 21:20 ` Dmitry Torokhov [this message]
2018-05-02 7:07 ` David Engraf
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=20180430212007.GC54182@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=david.engraf@sysgo.com \
--cc=linux-input@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).