netdev - Re: [PATCH 05/11] pcmcia: do not use io_req_t when calling pcmcia_request

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

Date:	Sun, 01 Aug 2010 11:04:37 -0700
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Dominik Brodowski <linux@...inikbrodowski.net>
Cc:	linux-pcmcia@...ts.infradead.org, netdev@...r.kernel.org,
	linux-wireless@...r.kernel.org, linux-ide@...r.kernel.org,
	linux-usb@...r.kernel.org, laforge@...monks.org,
	linux-mtd@...ts.infradead.org, linux-bluetooth@...r.kernel.org,
	alsa-devel@...a-project.org, linux-serial@...r.kernel.org,
	Michael Buesch <mb@...sch.de>
Subject: Re: [PATCH 05/11] pcmcia: do not use io_req_t when calling
 pcmcia_request_io()

Hi Dominik,

> Instead of io_req_t, drivers are now requested to fill out
> struct pcmcia_device *p_dev->resource[0,1] for up to two ioport
> ranges. After a call to pcmcia_request_io(), the ports found there
> are reserved, after calling pcmcia_request_configuration(), they may
> be used.
> 
> CC: netdev@...r.kernel.org
> CC: linux-wireless@...r.kernel.org
> CC: linux-ide@...r.kernel.org
> CC: linux-usb@...r.kernel.org
> CC: laforge@...monks.org
> CC: linux-mtd@...ts.infradead.org
> CC: linux-bluetooth@...r.kernel.org
> CC: alsa-devel@...a-project.org
> CC: linux-serial@...r.kernel.org
> CC: Michael Buesch <mb@...sch.de>
> Signed-off-by: Dominik Brodowski <linux@...inikbrodowski.net>

for the drivers/bluetooth/ pieces.

Acked-by: Marcel Holtmann <marcel@...tmann.org>

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html