From: Ryan Mallon <ryan@bluewatersys.com>
To: Remy Bohmer <linux@bohmer.net>
Cc: Harro Haan <hrhaan@gmail.com>,
Andrew Victor <avictor.za@gmail.com>,
David Brownell <dbrownell@users.sourceforge.net>,
H Hartley Sweeten <hartleys@visionengravers.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch v2 1/2] at91_udc.c read_fifo timing issue
Date: Mon, 01 Feb 2010 09:08:16 +1300 [thread overview]
Message-ID: <4B65E330.3040000@bluewatersys.com> (raw)
In-Reply-To: <3efb10971001290904p74b1919aif8ff013f050123a9@mail.gmail.com>
Remy Bohmer wrote:
> Hi Harro,
>
> 2010/1/29 Harro Haan <hrhaan@gmail.com>:
>> This solves the read_fifo timing issue for example seen with CDC Ethernet.
>> See the comments below for more info.
>>
>> Signed-off-by: Harro Haan <hrhaan@gmail.com>
>> ---
>> drivers/usb/gadget/at91_udc.c | 46 ++++++++++++++++++++++++++++++++++++++----
>> 1 file changed, 42 insertions(+), 4 deletions(-)
>>
> Acked-by: Remy Bohmer <linux@bohmer.net>
Can I get your Acked-by for my patch also Remy?
Harro, I can either submit my patch to the patch system separately, or
you can put it through with your series with my From/Signed-off-by tag
on it.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan@bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2010-01-31 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100129162029.998540038@gmail.com>
[not found] ` <20100129162155.824407360@gmail.com>
2010-01-29 17:27 ` [patch v2 2/2] at91_udc.c use spinlocks instead of local_irq_xxx H Hartley Sweeten
[not found] ` <20100129162155.709756286@gmail.com>
2010-01-29 17:04 ` [patch v2 1/2] at91_udc.c read_fifo timing issue Remy Bohmer
2010-01-31 20:08 ` Ryan Mallon [this message]
2010-01-31 22:34 ` Anti Sullin
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=4B65E330.3040000@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=avictor.za@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--cc=hartleys@visionengravers.com \
--cc=hrhaan@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@bohmer.net \
/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