From: Johan Hovold <johan@kernel.org>
To: "Ramachandran Srinivasan \(BRT-SG\)" <srinivasan.r@brtchip.com>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Deferred URB submission for timesharing the DMA channels of DWC_OTG host controller in Raspberry PI
Date: Mon, 8 Apr 2019 15:12:45 +0200 [thread overview]
Message-ID: <20190408131245.GC24108@localhost> (raw)
On Mon, Apr 08, 2019 at 11:54:00AM +0000, Ramachandran Srinivasan (BRT-SG) wrote:
Make sure to always provide a proper commit message.
> Signed-off-by: Srinivasan R <srinivasan.r@brtchip.com>
> ---
> drivers/usb/serial/ftdi_sio.c | 153 +++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 152 insertions(+), 1 deletion(-)
Your patch has been been (whitespace) corrupted and is barely readable.
I have no idea you're trying to here.
Johan
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: "Ramachandran Srinivasan (BRT-SG)" <srinivasan.r@brtchip.com>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Deferred URB submission for timesharing the DMA channels of DWC_OTG host controller in Raspberry PI
Date: Mon, 8 Apr 2019 15:12:45 +0200 [thread overview]
Message-ID: <20190408131245.GC24108@localhost> (raw)
Message-ID: <20190408131245.WdlG__nCkl9NRHrHFVNWI0vifGs_bFgr7SuWWh0YeLg@z> (raw)
In-Reply-To: <1554724399-2972-1-git-send-email-srinivasan.r@brtchip.com>
On Mon, Apr 08, 2019 at 11:54:00AM +0000, Ramachandran Srinivasan (BRT-SG) wrote:
Make sure to always provide a proper commit message.
> Signed-off-by: Srinivasan R <srinivasan.r@brtchip.com>
> ---
> drivers/usb/serial/ftdi_sio.c | 153 +++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 152 insertions(+), 1 deletion(-)
Your patch has been been (whitespace) corrupted and is barely readable.
I have no idea you're trying to here.
Johan
next reply other threads:[~2019-04-08 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 13:12 Johan Hovold [this message]
2019-04-08 13:12 ` [PATCH] Deferred URB submission for timesharing the DMA channels of DWC_OTG host controller in Raspberry PI Johan Hovold
-- strict thread matches above, loose matches on Subject: below --
2019-04-15 8:00 [v2] usb: serial: defer URB submission for ftdi_sio Johan Hovold
2019-04-15 8:00 ` [PATCH v2] " Johan Hovold
2019-04-10 8:56 Deferred URB submission for timesharing the DMA channels of DWC_OTG host controller in Raspberry PI Ramachandran Srinivasan (BRT-SG)
2019-04-10 8:56 ` [PATCH] " Ramachandran Srinivasan (BRT-SG)
2019-04-09 10:47 [v2] usb: serial: defer URB submission for ftdi_sio Ramachandran Srinivasan (BRT-SG)
2019-04-09 10:47 ` [PATCH v2] " Ramachandran Srinivasan (BRT-SG)
2019-04-08 15:52 Deferred URB submission for timesharing the DMA channels of DWC_OTG host controller in Raspberry PI Sergei Shtylyov
2019-04-08 15:52 ` [PATCH] " Sergei Shtylyov
2019-04-08 11:54 Ramachandran Srinivasan (BRT-SG)
2019-04-08 11:54 ` [PATCH] " Ramachandran Srinivasan (BRT-SG)
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=20190408131245.GC24108@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=srinivasan.r@brtchip.com \
/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.