mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Martyn Welch <martyn@welchs.me.uk>,
	Manohar Vanga <manohar.vanga@gmail.com>,
	devel@driverdev.osuosl.org, Igor Alekseev <igor.alekseev@itep.ru>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv5] staging: vme_user: provide DMA functionality
Date: Sun, 18 Oct 2015 00:00:54 -0400	[thread overview]
Message-ID: <89FDDCCD-975D-4A84-B1B0-C174C170C4C6@gmail.com> (raw)
In-Reply-To: <20151018035227.GA9898@kroah.com>


> On 2015/10/17, at 23:52, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> 
> On Sun, Oct 11, 2015 at 03:13:25AM +0300, Dmitry Kalinkin wrote:
>> This introduces a new dma device that provides a single ioctl call that
>> provides DMA read and write functionality to the user space.
>> 
>> Signed-off-by: Dmitry Kalinkin <dmitry.kalinkin@gmail.com>
>> Cc: Igor Alekseev <igor.alekseev@itep.ru>
>> ---                                                                             
>> 
> 
> Ugh, trailing whitespace hurts the eyes...
> 
> Anyway, I need an ack from Martyn before I can accept this type of
> thing.
> 
> thanks,
> 
> greg k-h

This fail is sponsored by vim :set colorcolumn=80 + clipboard copy-paste.

  reply	other threads:[~2015-10-18  4:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-10 22:25 [PATCHv4 RESEND] " Dmitry Kalinkin
2015-10-10 23:53 ` kbuild test robot
2015-10-11  0:13   ` [PATCHv5] " Dmitry Kalinkin
2015-10-18  3:52     ` Greg Kroah-Hartman
2015-10-18  4:00       ` Dmitry Kalinkin [this message]
2015-10-18 14:31     ` Martyn Welch
2015-10-18 17:53       ` Dmitry Kalinkin
2015-10-18 18:13         ` [PATCHv6] " Dmitry Kalinkin
2015-10-18 22:04         ` [PATCHv5] " Martyn Welch
2015-10-19  8:26           ` Alessio Igor Bogani
2015-10-19  9:19           ` Dmitry Kalinkin
2015-10-19  9:46             ` Alessio Igor Bogani

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=89FDDCCD-975D-4A84-B1B0-C174C170C4C6@gmail.com \
    --to=dmitry.kalinkin@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=igor.alekseev@itep.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manohar.vanga@gmail.com \
    --cc=martyn@welchs.me.uk \
    /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
all inboxes | Powered by JetHome®