From: Andrew Morton <akpm@linux-foundation.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-kernel@vger.kernel.org, oakad@yahoo.com,
Greg KH <greg@kroah.com>
Subject: Re: [PATH 0/4] Memstick patches for 2.6.39
Date: Tue, 22 Mar 2011 16:21:08 -0700 [thread overview]
Message-ID: <20110322162108.a4b70291.akpm@linux-foundation.org> (raw)
In-Reply-To: <1300621371.15768.11.camel@maxim-laptop>
On Sun, 20 Mar 2011 13:42:51 +0200
Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> On Sat, 2011-03-19 at 23:47 -0700, Andrew Morton wrote:
> > On Sun, 20 Mar 2011 05:09:05 +0200 Maxim Levitsky <maximlevitsky@gmail.com> wrote:
> >
>
> ...
>
> Also, I don't have much time now to improve the ms_block driver till
> this summer (studying).
> The driver works. Yes it has a flaw in regard to scatterlist processing,
> because I didn't find a better way to deal with this monster, but I will
> fix that later. I am not the kind of guy that runs away after a merge.
> It would be nice to just see my code in kernel, code I wrote more that a
> year ago.
>
> This flaw is purely theoretical. Driver does work.
Lots of code is "flawed but works". The place for such code is
drivers/staging/ - it gets put in there so the code is available for
those who need the driver and the code is later moved over into
drivers/ once the flaws have been addressed.
So a path forward here would be for us to put the driver and the
sglist extensions into a directory under drivers/staging/.
next prev parent reply other threads:[~2011-03-22 23:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 4:16 [PATH 0/4] Memstick patches for 2.6.39 Maxim Levitsky
2011-03-04 4:16 ` [PATCH 1/4] scatterlist: new helper functions Maxim Levitsky
2011-03-06 7:29 ` FUJITA Tomonori
2011-03-06 15:14 ` Maxim Levitsky
2011-03-06 21:49 ` FUJITA Tomonori
2011-03-07 2:20 ` Maxim Levitsky
2011-03-09 17:24 ` Maxim Levitsky
2011-03-16 0:44 ` Andrew Morton
2011-03-16 2:35 ` FUJITA Tomonori
2011-03-16 4:18 ` Alex Dubov
2011-03-16 4:55 ` FUJITA Tomonori
2011-03-17 3:46 ` Alex Dubov
2011-03-17 3:57 ` James Bottomley
2011-03-16 22:33 ` Andrew Morton
2011-03-17 6:41 ` Alex Dubov
2011-03-17 13:17 ` Maxim Levitsky
2011-03-18 0:59 ` FUJITA Tomonori
2011-03-04 4:16 ` [PATCH 2/4] memstick: add support for legacy memorysticks Maxim Levitsky
2011-03-04 4:16 ` [PATCH 3/4] memstick: Add driver for Ricoh R5C592 card reader Maxim Levitsky
2011-03-16 4:25 ` Alex Dubov
2011-03-04 4:16 ` [PATCH 4/4] memstick: add Alex Dubov to MAINTAINERS of the memstick core Maxim Levitsky
2011-03-12 16:23 ` [PATH 0/4] Memstick patches for 2.6.39 Maxim Levitsky
2011-03-15 20:00 ` Maxim Levitsky
2011-03-15 21:04 ` Andrew Morton
2011-03-16 0:25 ` Maxim Levitsky
2011-03-20 3:09 ` Maxim Levitsky
2011-03-20 6:47 ` Andrew Morton
2011-03-20 11:42 ` Maxim Levitsky
2011-03-22 13:01 ` Maxim Levitsky
2011-03-22 23:21 ` Andrew Morton [this message]
2011-03-23 0:59 ` Maxim Levitsky
2011-03-23 3:42 ` Greg KH
2011-03-23 15:30 ` Maxim Levitsky
2011-03-24 3:27 ` 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=20110322162108.a4b70291.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=oakad@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.