linux-kernel - Re: [PATCH 1/2] memstick: add support for legacy memorysticks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Sat, 11 Dec 2010 20:13:44 -0800 (PST)
From:	Alex Dubov <oakad@...oo.com>
To:	Maxim Levitsky <maximlevitsky@...il.com>,
	Takashi Iwai <tiwai@...e.de>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Aries Lee <arieslee@...cron.com>
Subject: Re: [PATCH 1/2] memstick: add support for legacy memorysticks

--- On Sat, 11/12/10, Takashi Iwai <tiwai@...e.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.



      
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/