The patch titled acpi/dock: use NULL for pointer has been removed from the -mm tree. Its filename was acpi-dock-use-null-for-pointer.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ Subject: acpi/dock: use NULL for pointer From: Randy Dunlap <randy.dunlap@xxxxxxxxxx> Use NULL instead of 0 for pointers: drivers/acpi/dock.c:677:75: warning: Using plain integer as NULL pointer Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx> Cc: Len Brown <lenb@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/acpi/dock.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff -puN drivers/acpi/dock.c~acpi-dock-use-null-for-pointer drivers/acpi/dock.c --- a/drivers/acpi/dock.c~acpi-dock-use-null-for-pointer +++ a/drivers/acpi/dock.c @@ -29,6 +29,7 @@ #include <linux/notifier.h> #include <linux/platform_device.h> #include <linux/jiffies.h> +#include <linux/stddef.h> #include <acpi/acpi_bus.h> #include <acpi/acpi_drivers.h> @@ -674,7 +675,7 @@ static ssize_t show_dock_uid(struct devi struct device_attribute *attr, char *buf) { unsigned long lbuf; - acpi_status status = acpi_evaluate_integer(dock_station->handle, "_UID", 0, &lbuf); + acpi_status status = acpi_evaluate_integer(dock_station->handle, "_UID", NULL, &lbuf); if(ACPI_FAILURE(status)) { return 0; } _ Patches currently in -mm which might be from randy.dunlap@xxxxxxxxxx are git-acpi.patch git-drm.patch romfs-printk-format-warnings.patch git-netdev-all.patch git-scsi-misc.patch git-unionfs.patch git-ipwireless_cs.patch i386-fix-gdts-number-of-quadwords-in.patch scripts-kernel-doc-whitespace-cleanup.patch reiserfs-proc-support-requires-proc_fs.patch kprobes-fix-sparse-null-warning.patch ext4-use-null-for-pointers.patch some-grammatical-fixups-and-additions-to-atomich-kernel-doc.patch profile-likely-unlikely-macros.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html