From: Alex Dubov <oakad@yahoo.com>
To: Maxim Levitsky <maximlevitsky@gmail.com>, Takashi Iwai <tiwai@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Aries Lee <arieslee@jmicron.com>
Subject: Re: [PATCH 1/2] memstick: add support for legacy memorysticks
Date: Sat, 11 Dec 2010 20:13:44 -0800 (PST) [thread overview]
Message-ID: <266179.95268.qm@web37601.mail.mud.yahoo.com> (raw)
In-Reply-To: <s5hsjy4bqxi.wl%tiwai@suse.de>
--- On Sat, 11/12/10, Takashi Iwai <tiwai@suse.de> wrote:
>
> > Takashi, you are welcome to look at my version of
> code, the one that
> > Alex mostly refuses to merge.
> > It is located at http://gitorious.org/ricoh-kernel/ricoh-kernel
> > (This contains everything I did for ricoh and
> jmicron)
> > Try this code and see if MS standard works for you in
> parallel mode.
> >
> > If it doesn't, every module contains built-in
> debugging, activated by
> > debug=1 or 2 module parameter, yet another thing Alex
> refused to
> > consider.
This should be done through a common kernel infrastructure.
It was added there for a reason.
>
> It's an unfortunate situation. I see the point Alex
> mentioned (small
> changes first), but honestly, I don't understand why this
> kind of
> patches has to be blocked, too. It's basically an
> addition for the
> support of missing device types.
>
I never said I have any opposition to supporting other device types.
My proposal was, from the very beginning, to merge new drivers first,
than discuss changes to the existing stuff.
next parent reply other threads:[~2010-12-12 4:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5hsjy4bqxi.wl%tiwai@suse.de>
2010-12-12 4:13 ` Alex Dubov [this message]
2010-12-09 2:39 MEMSTICK: Add my 2 drivers Maxim Levitsky
2010-12-09 2:42 ` [PATCH 1/2] memstick: add support for legacy memorysticks Maxim Levitsky
2010-12-09 7:19 ` Takashi Iwai
2010-12-09 11:56 ` Takashi Iwai
2010-12-09 15:44 ` Takashi Iwai
2010-12-10 22:34 ` Maxim Levitsky
2010-12-09 21:09 ` Andrew Morton
2010-12-10 22:27 ` Maxim Levitsky
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=266179.95268.qm@web37601.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=arieslee@jmicron.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=tiwai@suse.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