All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: fei phung <feiphung27@gmail.com>
Cc: linux-fpga@vger.kernel.org
Subject: Re: [PATCH] Add RIFFA PCIe driver to staging tree
Date: Mon, 15 Oct 2018 12:47:09 +0200	[thread overview]
Message-ID: <20181015104709.GA26218@kroah.com> (raw)
In-Reply-To: <CAF8QhUjTZB8YO-eBJM1TLfKfi91JR6cexAD_ApGn9KWs1VGEHg@mail.gmail.com>

On Mon, Oct 15, 2018 at 06:41:31PM +0800, fei phung wrote:
> Please the patch below or the email attachment
> 
> For reference, please see
> https://github.com/promach/riffa/tree/full_duplex/driver/linux
> 
> phung@UbuntuHW15:~/linux$ cat
> patches/0001-Added-a-full-duplex-riffa-PCIe-linux-staging-driver..patch
> >From 7c3050c7e86017d85c75c640ea38376f505b2763 Mon Sep 17 00:00:00 2001
> From: promach <feiphung@hotmail.com>
> Date: Mon, 15 Oct 2018 18:28:16 +0800
> Subject: [PATCH] Added a full duplex riffa PCIe linux staging driver.
>  Signed-off-by: PHUNG CHENG FEI (feiphung@hotmail.com)
> 
> ---
>  drivers/staging/riffa/Makefile       |  157 +++
>  drivers/staging/riffa/README.txt     |   38 +
>  drivers/staging/riffa/circ_queue.c   |  188 +++
>  drivers/staging/riffa/circ_queue.h   |   96 ++
>  drivers/staging/riffa/riffa.c        |  152 +++
>  drivers/staging/riffa/riffa.h        |  121 ++
>  drivers/staging/riffa/riffa_driver.c | 1633 ++++++++++++++++++++++++++
>  drivers/staging/riffa/riffa_driver.h |  131 +++
>  8 files changed, 2516 insertions(+)
>  create mode 100644 drivers/staging/riffa/Makefile
>  create mode 100644 drivers/staging/riffa/README.txt
>  create mode 100644 drivers/staging/riffa/circ_queue.c
>  create mode 100644 drivers/staging/riffa/circ_queue.h
>  create mode 100644 drivers/staging/riffa/riffa.c
>  create mode 100644 drivers/staging/riffa/riffa.h
>  create mode 100644 drivers/staging/riffa/riffa_driver.c
>  create mode 100644 drivers/staging/riffa/riffa_driver.h

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
  and can not be applied.  Please read the file,
  Documentation/email-clients.txt in order to fix this.

- Your patch was attached, please place it inline so that it can be
  applied directly from the email message itself.

- You did not specify a description of why the patch is needed, or
  possibly, any description at all, in the email body.  Please read the
  section entitled "The canonical patch format" in the kernel file,
  Documentation/SubmittingPatches for what is needed in order to
  properly describe the change.

- You did not write a descriptive Subject: for the patch, allowing Greg,
  and everyone else, to know what this patch is all about.  Please read
  the section entitled "The canonical patch format" in the kernel file,
  Documentation/SubmittingPatches for what a proper Subject: line should
  look like.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

       reply	other threads:[~2018-10-15 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF8QhUjTZB8YO-eBJM1TLfKfi91JR6cexAD_ApGn9KWs1VGEHg@mail.gmail.com>
2018-10-15 10:47 ` Greg KH [this message]
     [not found] <SG2PR06MB31763736BF5D2F346D19C12EC1FE0@SG2PR06MB3176.apcprd06.prod.outlook.com>
     [not found] ` <SG2PR06MB3176B20AA8DAB164A73568B7C1FE0@SG2PR06MB3176.apcprd06.prod.outlook.com>
2018-10-16  8:27   ` [PATCH] Add RIFFA PCIe driver to staging tree gregkh

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=20181015104709.GA26218@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=feiphung27@gmail.com \
    --cc=linux-fpga@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.