linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: Michal Nazarewicz <m.nazarewicz@samsung.com>, linux-usb@vger.kernel.org
Cc: Michal Nazarewicz <mina86@mina86.com>, Greg KH <greg@kroah.com>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Davide Libenzi <davidel@xmailserver.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv4 0/8] The FunctionFS composite function
Date: Thu, 06 May 2010 10:44:39 +0200	[thread overview]
Message-ID: <op.vb9zwpwj7p4s8u@pikus> (raw)
In-Reply-To: <cover.1273054944.git.mina86@mina86.com>

On Wed, 05 May 2010 12:53:10 +0200, Michal Nazarewicz <m.nazarewicz@samsung.com> wrote:
> The code has been tested with a user-space MTP driver and there was no
> problems including with setup requests.  As such, it is believed that
> the data transfers are reliable.


> At this point I have to admit that communication on EP0 has not yet
> been tested, so beware of bugs there.

This last sentence is of course incorrect.  EP0 has been tested as well
as the first sentence implies.  Again forgot to edit the whole cover
letter.  Sorry about the confusion.

-- 
Best regards,                                        _     _
| Humble Liege of Serenely Enlightened Majesty of  o' \,=./ `o
| Computer Science,  Michał "mina86" Nazarewicz       (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--

      parent reply	other threads:[~2010-05-06  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 10:53 [PATCHv4 0/8] The FunctionFS composite function Michal Nazarewicz
2010-05-05 10:53 ` [PATCHv4 1/8] wait_event_interruptible_locked() interface Michal Nazarewicz
2010-05-05 10:53   ` [PATCHv4 2/8] fs/timerfd.c: make use of wait_event_interruptible_locked_irq() Michal Nazarewicz
2010-05-06  8:44 ` Michał Nazarewicz [this message]

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=op.vb9zwpwj7p4s8u@pikus \
    --to=m.nazarewicz@samsung.com \
    --cc=davidel@xmailserver.org \
    --cc=greg@kroah.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mina86@mina86.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).