All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Eli Billauer <eli.billauer@gmail.com>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de
Subject: Re: [PATCH v2 2/2] New driver: Xillybus generic interface for FPGA (programmable logic)
Date: Fri, 30 Nov 2012 08:35:19 -0800	[thread overview]
Message-ID: <20121130163519.GC4478@kroah.com> (raw)
In-Reply-To: <50B8D069.8070608@gmail.com>

On Fri, Nov 30, 2012 at 05:27:37PM +0200, Eli Billauer wrote:
> I made changes in the code as a response to almost all your comments
> to my best understanding.
> 
> I also sent a separate mail responding to a couple of issues, which
> seems not have reached you.

I now see it, sorry for the grumpy pre-coffee response I made earlier.

> But to put it short:
> 
> * The pci_ids: I wasn't sure if I should remove only my own product
> ID or all the vendor IDs, and this is clear now.

Good.

> * As for the documentation, I don't quite understand what I should
> add. There's a rather extensive documentation for download at the
> site. The docs for the host side mostly instruct common UNIX
> programming techniques: The device files are just data pipes to
> FIFOs in the FPGA, behaving like one would expect.

You need to document the user/kernel API that you have now created for
this driver, either in the Documentation directory, or in the very
least, the driver submission changelog entry.  Otherwise we don't know
where to look, nor if those docs are even correct anymore.

> * As for the special class issue: When Xillybus is used, the whole
> system's mission is usually around it (e.g. it's a computer doing
> data acquisition through the Xillybus pipes). So giving it a high
> profile makes sense, I believe. Besides, a dozen of device files are
> not rare. Needless to say, I'm not going to insist on this.

Good, please use misc device, for the reasons I suggested in my other
email.

> Other than that, it's all changes in the code. It's a major change
> there.

I don't understand what these sentances mean.

greg k-h

  reply	other threads:[~2012-11-30 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30 14:51 [PATCH v2 1/2] pci_ids: Added FPGA-related entries Eli Billauer
2012-11-30 14:51 ` [PATCH v2 2/2] New driver: Xillybus generic interface for FPGA (programmable logic) Eli Billauer
2012-11-30 15:09   ` Greg KH
2012-11-30 15:27     ` Eli Billauer
2012-11-30 16:35       ` Greg KH [this message]
2012-11-30 15:08 ` [PATCH v2 1/2] pci_ids: Added FPGA-related entries Greg KH

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=20121130163519.GC4478@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 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.