From: Greg KH <greg@kroah.com>
To: "Hans J. Koch" <hjk@linutronix.de>
Cc: Brandon Philips <brandon@ifup.org>, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] uio: add the uio_aec driver
Date: Wed, 4 Feb 2009 15:07:33 -0800 [thread overview]
Message-ID: <20090204230733.GE18484@kroah.com> (raw)
In-Reply-To: <20090129232615.GC3036@local>
On Fri, Jan 30, 2009 at 12:26:17AM +0100, Hans J. Koch wrote:
> On Tue, Jan 27, 2009 at 01:00:04PM -0800, Brandon Philips wrote:
> > UIO driver for the Adrienne Electronics Corporation PCI time code
> > device.
>
> Sorry for not reviewing this earlier, I was quite busy this week and didn't
> work at my home office.
> I know I'm a bit late, since Greg already added it to his tree, but I reviewed
> it anyway. Nice piece of work. I've got no objections either.
>
> >
> > This device differs from other UIO devices since it uses I/O ports instead of
> > memory mapped I/O. In order to make it possible for UIO to work with this
> > device a utility, uioport, can be used to read and write the ports.
> >
> > uioport is designed to be a setuid program and checks the permissions of
> > the /dev/uio* node and if the user has write permissions it will use
> > iopl and out*/in* to access the device.
> >
> > [1] git clone git://ifup.org/philips/uioport.git
> >
> > Signed-off-by: Brandon Philips <brandon@ifup.org>
>
> Signed-off-by: Hans J. Koch <hjk@linutronix.de>
Thanks for the review, I've added your signed-off-by to the patch in my
queue.
greg k-h
prev parent reply other threads:[~2009-02-04 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 20:47 uio: add the uio_aec driver Brandon Philips
2009-01-20 21:48 ` Hans J. Koch
2009-01-21 17:01 ` Brandon Philips
2009-01-21 20:06 ` Hans J. Koch
2009-01-27 21:00 ` [PATCHv2] " Brandon Philips
2009-01-29 23:26 ` Hans J. Koch
2009-02-04 23:07 ` Greg KH [this message]
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=20090204230733.GE18484@kroah.com \
--to=greg@kroah.com \
--cc=brandon@ifup.org \
--cc=gregkh@suse.de \
--cc=hjk@linutronix.de \
--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