All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: edward_estabrook@agilent.com
Cc: linux-kernel@vger.kernel.org, hjk@linutronix.de,
	edward.estabrook@gmail.com, edward.estabrook.lkml@gmail.com
Subject: Re: [PATCH 1/1] Userspace I/O (UIO): Add support for userspace DMA
Date: Wed, 3 Dec 2008 16:50:55 -0800	[thread overview]
Message-ID: <20081204005055.GE6981@suse.de> (raw)
In-Reply-To: <43FC624C55D8C746A914570B66D642610367F29B@cos-us-mb03.cos.agilent.com>

On Wed, Dec 03, 2008 at 02:39:44PM -0700, edward_estabrook@agilent.com wrote:
> @@ -82,6 +94,16 @@ static inline int __must_check  extern void uio_unregister_device(struct uio_info *info);  extern void uio_event_notify(struct uio_info *info);
>  
> +/* uio_dev_get_name - return the name associated with this uio device 
> +*/ extern char *uio_dev_get_name(struct uio_device *idev);
> +
> +/* Starting index assigned to dynamically allocated regions. */ #define 
> +UIO_DMA_MEM_BASE_INDEX 1000
> +
> +/* mmap dynamically allocates a DMA memory block if
> + * its offset parameter matches this value. */ #define 
> +UIO_DMA_MEM_ALLOCATE_VM_PGOFF_MAGIC 0xFFFFFUL

Something looks wrong with this patch, is it line wrapped somehow?

odd.

thanks,

greg k-h

  parent reply	other threads:[~2008-12-04  0:52 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 21:39 [PATCH 1/1] Userspace I/O (UIO): Add support for userspace DMA edward_estabrook
2008-12-03 22:00 ` Leon Woestenberg
2008-12-04  2:44   ` Edward Estabrook
2008-12-04  0:49 ` Greg KH
2008-12-04  0:50 ` Greg KH [this message]
2008-12-04  1:49   ` Edward Estabrook
2008-12-04  8:39 ` Peter Zijlstra
2008-12-04  8:39   ` Peter Zijlstra
2008-12-04 10:27   ` Hugh Dickins
2008-12-04 10:27     ` Hugh Dickins
2008-12-23 21:32     ` Max Krasnyansky
2008-12-23 21:32       ` Max Krasnyansky
2008-12-04 18:08   ` Hans J. Koch
2008-12-04 18:08     ` Hans J. Koch
2008-12-05  7:10     ` Peter Zijlstra
2008-12-05  7:10       ` Peter Zijlstra
2008-12-05  9:44       ` Hans J. Koch
2008-12-05  9:44         ` Hans J. Koch
2008-12-06  0:32         ` Edward Estabrook
2008-12-06  0:32           ` Edward Estabrook
2008-12-12 17:25           ` Peter Zijlstra
2008-12-13  0:29             ` Hans J. Koch
2009-12-12  0:02   ` Earl Chew
2009-12-12  0:02     ` Earl Chew
2009-12-14 19:23     ` Hans J. Koch
2009-12-14 19:23       ` Hans J. Koch
2009-12-15 13:34       ` Earl Chew
2009-12-15 13:34         ` Earl Chew
2009-12-15 17:47         ` Earl Chew
2009-12-15 17:47           ` Earl Chew
2009-12-15 21:33           ` Hans J. Koch
2009-12-15 21:33             ` Hans J. Koch
2009-12-15 21:00         ` Hans J. Koch
2009-12-15 21:00           ` Hans J. Koch
2009-12-15 21:47           ` Earl Chew
2009-12-15 21:47             ` Earl Chew
2009-12-15 22:28             ` Hans J. Koch
2009-12-15 22:28               ` Hans J. Koch
2009-12-16  0:20               ` Earl Chew
2009-12-16  0:20                 ` Earl Chew
2009-12-16  1:23                 ` Hans J. Koch
2009-12-16  1:23                   ` Hans J. Koch
2009-12-16  1:45                   ` Earl Chew
2009-12-16  1:45                     ` Earl Chew

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=20081204005055.GE6981@suse.de \
    --to=gregkh@suse.de \
    --cc=edward.estabrook.lkml@gmail.com \
    --cc=edward.estabrook@gmail.com \
    --cc=edward_estabrook@agilent.com \
    --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 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.