From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] s3c2410_udc: 2440 dual packet workaround
Date: Wed, 23 Sep 2009 22:29:18 +0300 [thread overview]
Message-ID: <200909232230.03982.anarsoul@gmail.com> (raw)
In-Reply-To: <164376.11955.qm@web54401.mail.yahoo.com>
? ????????? ?? 23 ???????? 2009 22:20:05 ????? David Anders ???????:
> Vasily,
>
> i have tried this patch on a number of S3C2440 based systems and found that
> this patch is not a completely effective solution. if the purpose is to
> get a solution even if it is an incomplete one, then i'd be ok with this
> patch, however, i'm not keen on accepting a patch into the main tree with
> the knowledge that it isn't 100% effective.
Hi, Dave
s3c2410_udc driver is almost useless (at least it's very inconvenient) on
s3c244x machines without this patch. I think it's much better to have
incomplete solution than broken driver.
Btw, I can resend patchset without this patch if maintainer of this driver
thinks that accepting this patch is bad idea.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20090923/1db519e5/attachment.sig>
next prev parent reply other threads:[~2009-09-23 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 7:46 [PATCH 1/5] s3c2410_udc: 2440 dual packet workaround Vasily Khoruzhick
2009-09-23 19:20 ` David Anders
2009-09-23 19:29 ` Vasily Khoruzhick [this message]
[not found] ` <200909240711.17683.fg@emlix.com>
2009-09-24 19:38 ` Vasily Khoruzhick
2009-09-25 4:32 ` Fabian Godehardt
2009-09-24 0:27 ` Ben Dooks
2009-09-23 19:24 ` Robert Jarzmik
2009-09-23 19:35 ` Vasily Khoruzhick
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=200909232230.03982.anarsoul@gmail.com \
--to=anarsoul@gmail.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).