linux-kernel - Re: [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports both MCI slots used at the same time

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090612112900.4435f70f@hskinnemoen-d830>
Date:	Fri, 12 Jun 2009 11:29:00 +0200
From:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
To:	Nicolas Ferre <nicolas.ferre@...el.com>
Cc:	Rob Emanuele <poorarm@...reis.com>,
	Andrew Victor <avictor.za@...il.com>,
	Joey Oravec <joravec@...wtech.com>,
	linux-arm-kernel@...ts.arm.linux.org.uk,
	linux-kernel@...r.kernel.org, drzeus-mmc@...eus.cx
Subject: Re: [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports
 both 	MCI slots used at the same time

Nicolas Ferre wrote:
> > Well, what is the best way to differentiate it from the at91_mci
> > driver and keep users from trying to use both drivers?  
> 
> I propose that we setup a kind of choice sub menu in the Kconfig for
> those two drivers when they are both supported.

Shouldn't it be enough to simply add

	depends on !THE_OTHER_DRIVER

to both of them?

Btw, what are the long-term plans for this? Should the at91_mci driver
be phased out once the atmel-mci driver supports all at91 and avr32
devices?

> > Who would that be as I haven't seen anyone who maintains any of those
> > boards other than the at91rm8200 (at least nothing listed in the
> > MAINTAINERS file)?  The board-sam9g20ek.c platform only shows Atmel as
> > the most recent copyright.  
> 
> Hey, AT91 are very well maintained, SAM9 as well as at91rm9200.
> So, AT91 specific bits should be sent to this mailing-list with Andrew
> Victor in copy.
> I will also certainly add comments on this code.

One of you should update MAINTAINERS to reflect this.

Haavard
--
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/