From: "Alex Dubov" <oakad@yahoo.com>
To: "LKML" <linux-kernel@vger.kernel.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Maxim Levitsky" <maximlevitsky@gmail.com>
Subject: memstick: Alternative approach to proposed fixes
Date: Wed, 27 Oct 2010 04:41:07 +1100 [thread overview]
Message-ID: <1288114871-805-1-git-send-email-oakad@yahoo.com> (raw)
As I was not able to convince myself that profound changes proposed by Maxim
are really necessary, I propose to follow a much milder path with this update
round (as I outlined in my previous emails).
In this small patchset, I fix a couple of small omissions as well as introduce
support for "extended command" MSPro transfer method (currently enabled for
JMicron, but I'll clear the TI host for this functionality soon). I expect the
current solution to scale trivially for HG and XC transfer methods (I don't
have the spec for the later yet).
I'm still investigating possible issues with JMicron adapter. As JMicron is
known to follow a rather uneven path with their chip revisions, revision
dependent quirks may need to be introduced in the driver if I'm unable to
confirm Maxim's findings.
next reply other threads:[~2010-10-26 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 17:41 Alex Dubov [this message]
2010-10-26 17:41 ` [PATCH 1/4] memstick: avert possible race condition between idr_pre_get and idr_get_new Alex Dubov
2010-10-26 17:41 ` [PATCH 2/4] memstick: remove mspro_block_mutex Alex Dubov
2010-10-26 17:41 ` [PATCH 3/4] memstick: factor out transfer initiating functionality in mspro_block.c Alex Dubov
2010-10-26 17:41 ` [PATCH 4/4] memstick: add support for MSPro specific data transfer method Alex Dubov
2010-10-26 22:55 ` memstick: Alternative approach to proposed fixes Maxim Levitsky
2010-10-26 23:07 ` Maxim Levitsky
2010-10-26 23:08 ` Maxim Levitsky
2010-10-27 6:20 ` Alex Dubov
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=1288114871-805-1-git-send-email-oakad@yahoo.com \
--to=oakad@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome