[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X/bzBobubF1C5x3Q@kroah.com>
Date: Thu, 7 Jan 2021 12:39:50 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Eli Billauer <eli.billauer@...il.com>
Cc: arnd@...db.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] char: xillybus: Add driver for XillyUSB (Xillybus
variant for USB)
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
Powered by blists - more mailing lists