From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] s3c2410_udc: fix custom UDC command handling
Date: Mon, 20 Jun 2011 18:15:23 +0300 [thread overview]
Message-ID: <20110620151522.GN14262@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1106201105430.2113-100000@iolanthe.rowland.org>
Hi,
On Mon, Jun 20, 2011 at 11:07:51AM -0400, Alan Stern wrote:
> On Mon, 20 Jun 2011, Viliam Mateicka wrote:
>
> > So, will somebody at least react/reply (or just fix) ?
>
> Have some patience. You did not address your email message to either
> of the driver's authors or to the current Gadget maintainer. Also,
> David Brownell is deceased and Greg KH is on vacation.
besides, the patch formatting is wrong. That was noted before and the
reply was less than acceptably polite, so unless the patch comes
Perfect(TM), I'm not looking into it.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110620/ab068081/attachment.sig>
next prev parent reply other threads:[~2011-06-20 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 8:04 [PATCH] s3c2410_udc: fix custom UDC command handling Viliam Mateicka
2011-06-20 8:25 ` Viliam Mateicka
2011-06-20 15:07 ` Alan Stern
2011-06-20 15:15 ` Felipe Balbi [this message]
2011-06-20 15:20 ` Skacore Systems
2011-06-20 15:36 ` Felipe Balbi
2011-06-20 15:48 ` Skacore Systems
2011-06-20 15:57 ` Skacore Systems
2011-06-20 16:06 ` Felipe Balbi
2011-06-20 16:41 ` Skacore Systems
2011-06-20 17:05 ` Felipe Balbi
2011-06-20 17:27 ` Viliam Mateicka
2011-06-20 17:34 ` Felipe Balbi
2011-06-20 19:05 ` Viliam Mateicka
2011-06-20 16:07 ` Jassi Brar
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=20110620151522.GN14262@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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 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).