linux-kernel - Re: [PATCH v2 0/3] Add SDHCI ACPI driver

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:	Fri, 23 Nov 2012 21:35:22 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Adrian Hunter <adrian.hunter@...el.com>
Cc:	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	Chris Ball <cjb@...top.org>, mika.westerberg@...ux.intel.com,
	linux-mmc@...r.kernel.org, linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] Add SDHCI ACPI driver

On Friday, November 23, 2012 01:35:58 PM Adrian Hunter wrote:
> Hi
> 
> Here is SDHCI ACPI driver.
> 
> Changes for v2:
> 
> 	Dropped "PNPACPI: exclude SDHCI devices"
> 	Added "PNPACPI: exclude devices already bound"
> 	Changed dev->acpi_handle to ACPI_HANDLE(dev)
> 	Added Chris' Ack for sdhci-acpi
> 
> 
> Adrian Hunter (2):
>       ACPI: add SDHCI to ACPI platform devices
>       mmc: sdhci-acpi: add SDHCI ACPI driver
> 
> Mika Westerberg (1):
>       PNPACPI: exclude devices already bound

Applied to linux-pm.git/linux-next as v3.8 material.

Next time, however, I'll really prefer it if your changelogs (1) exist and (2)
are more descriptive than the (existing) ones in this series.

I added the changelogs for you (please check in the tree above if they make
sense), but that's not something I should be doing in general I think.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/