From: Greg KH <gregkh@linuxfoundation.org>
To: Eli Billauer <eli.billauer@gmail.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] char: xillybus: Add driver for XillyUSB (Xillybus variant for USB)
Date: Thu, 7 Jan 2021 12:39:50 +0100 [thread overview]
Message-ID: <X/bzBobubF1C5x3Q@kroah.com> (raw)
In-Reply-To: <5FF6EDED.40408@gmail.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Thu, Jan 07, 2021 at 01:18:05PM +0200, Eli Billauer wrote:
> Hello, Greg.
>
> I'm afraid we're not on the same page. As mentioned in the original patch
> description, XillyUSB and the existing Xillybus variant presents a nearly
> identical API. User space programs see no difference when using one or the
> other, except for different device file names.
My point is, do NOT have different file names. Userspace should not
care about the backing transport layer of a device.
> In that sense, it's exactly
> like tty devices. But unlike ttys, there are no ioctls or any other special
> API functions to export. Xillybus' API consists only of the basic file
> operations, which behave like you'd expect from a pipe, more or less.
Great, then do like the tty devices do and present the same device name
to userspace.
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-07 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 17:05 [PATCH] char: xillybus: Add driver for XillyUSB (Xillybus variant for USB) eli.billauer
2020-12-13 17:22 ` Randy Dunlap
2020-12-13 17:30 ` Eli Billauer
2021-01-05 13:47 ` Greg KH
2021-01-06 14:03 ` Eli Billauer
2021-01-06 14:23 ` Greg KH
2021-01-07 11:18 ` Eli Billauer
2021-01-07 11:39 ` Greg KH [this message]
2021-01-08 10:59 ` Eli Billauer
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=X/bzBobubF1C5x3Q@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=eli.billauer@gmail.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