- 25 Jan, 2008 25 commits
-
-
Tony Jones authored
struct class_device is going away, this converts the code to use struct device instead. Signed-off-by:
Tony Jones <tonyj@suse.de> Cc: Tim Waugh <tim@cyberelk.net> Cc: Jens Axboe <axboe@kernel.dk> Cc: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Tony Jones authored
struct class_device is going away, this converts the code to use struct device instead. Signed-off-by:
-
Tony Jones authored
struct class_device is going away, this converts the code to use struct device instead. Signed-off-by:
-
Tony Jones authored
struct class_device is going away, this converts the code to use struct device instead. Signed-off-by:
-
Tony Jones authored
Signed-off-by:
Karsten Keil <kkeil@suse.de> Signed-off-by:
-
Tony Jones authored
Signed-off-by:
-
Tony Jones authored
Signed-off-by:
Dan Williams <dan.j.williams@intel.com> Cc: Shannon Nelson <shannon.nelson@intel.com> Cc: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by:
-
Kay Sievers authored
Signed-off-by:
Kay Sievers <kay.sievers@vrfy.org> Cc: Tony Jones <tonyj@suse.de> Cc: Jan Harkes <jaharkes@cs.cmu.edu> Signed-off-by:
-
Tony Jones authored
Signed-off-by:
-
Evgeniy Polyakov authored
This adds kref_set() to the kref api for future use by people who really know what they are doing with krefs... From: Evgeniy Polyakov <johnpol@2ka.mipt.ru> Cc: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: -
Rafael J. Wysocki authored
This patch reorganizes the way suspend and resume notifications are sent to drivers. The major changes are that now the PM core acquires every device semaphore before calling the methods, and calls to device_add() during suspends will fail, while calls to device_del() during suspends will block. It also provides a way to safely remove a suspended device with the help of the PM core, by using the device_pm_schedule_removal() callback introduced specifically for this purpose, and updates two drivers (msr and cpuid) that need to use it. Signed-off-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
Rafael J. Wysocki <rjw@sisk.pl> Signed-off-by:
-
Greg Kroah-Hartman authored
As pointed out by Kay. Cc: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: -
Robert P. J. Day authored
Signed-off-by:Robert P. J. Day <rpjday@crashcourse.ca>
-
Frank Seidel authored
This is a driver to control the cardbus wireless data card that works on 3g networks. Greg Kroah-Hartman <gregkh@suse.de> did the initial driver cleanup. Thanks to Arnaud Patard <apatard@mandriva.com> for help with bugfixing. Thanks to Alan Cox for a lot of tty fixes. Thanks to Satyam Sharma <satyam@infradead.org> for fixing buildbreakage. Thanks to Frank Seidel <fseidel@suse.de> for a lot of bugfixes and rewriting to make it a sane Linux driver Thanks to Jiri Slaby <jirislaby@gmail.com> for a lot bugfixes, cleanups and rewrites that make it much more readable. Signed-off-by:
Frank Seidel <fseidel@suse.de> Signed-off-by:
Jiri Slaby <jirislaby@gmail.com>
-
Jean Delvare authored
Signed-off-by:
Jean Delvare <khali@linux-fr.org> Signed-off-by:
-
Zhang Le authored
Signed-off-by:
Zhang Le <r0bertz@gentoo.org> Signed-off-by:
Li Yang <leo@zh-kernel.org> Signed-off-by:
-
Li Yang authored
Signed-off-by:
-
Bryan Wu authored
Signed-off-by:
Bryan Wu <bryan.wu@analog.com> Signed-off-by:
-
TripleX Chung authored
Signed-off-by:
TripleX Chung <triplex@zh-kernel.org> Signed-off-by:
-
Dave Young authored
Signed-off-by:
Dave Young <hidave.darkstar@gmail.com> Signed-off-by:
-
Li Yang authored
Signed-off-by:
-
TripleX Chung authored
Signed-off-by:
-
Li Yang authored
The email address of the man-pages maintainer has changed. Cc: Michael Kerrisk <mtk.manpages@googlemail.com> Signed-off-by:
-
Li Yang authored
Rephrase the introduction as suggested by Jesper Juhl. Signed-off-by:
-
Li Yang authored
Update translation for commit be388494. Signed-off-by:
-
- 24 Jan, 2008 15 commits
-
-
Linus Torvalds authored
-
Kalle Valo authored
Before transmission of the last word in PIO RX_ONLY mode rx+tx mode is enabled: /* prevent last RX_ONLY read from triggering * more word i/o: switch to rx+tx */ if (c == 0 && tx == NULL) mcspi_write_cs_reg(spi, OMAP2_MCSPI_CHCONF0, l); But because c is decremented after the test, c will never be zero and rx+tx will not be enabled. This breaks RX_ONLY mode PIO transfers. Fix it by decrementing c in the beginning of the various I/O loops. Signed-off-by:
Kalle Valo <kalle.valo@nokia.com> Signed-off-by:
David Brownell <dbrownell@users.sourceforge.net> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
Linus Torvalds <torvalds@linux-foundation.org>
-
Linus Torvalds authored
This reverts commit 81100eb8 for the release, to avoid the unnecessary warning noise that is only really relevant to wireless driver developers. The warning will probably go right back in after I cut the release, but at least we won't unnecessarily worry users. Acked-by:
John W. Linville <linville@tuxdriver.com> Signed-off-by:
-
git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6Linus Torvalds authored
* git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6: [SPARC64]: Partially revert "Constify function pointer tables."
-
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6Linus Torvalds authored
* 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6: Revert "ACPI: Fan: Drop force_power_state acpi_device option" ACPI: EC: "DEBUG" needs to be defined earlier ACPI: EC: add leading zeros to debug messages ACPI: EC: fix dmesg spam regression ACPI: DMI blacklist to reduce console warnings on OSI(Linux) systems. ACPI: Add ThinkPad R61, ThinkPad T61 to OSI(Linux) white-list ACPI: make _OSI(Linux) console messages smarter ACPI: Delete Intel Customer Reference Board (CRB) from OSI(Linux) DMI list ACPI: on OSI(Linux), print needed DMI rather than requesting dmidecode output ACPI: create acpi_dmi_dump() DMI: create dmi_get_slot() DMI: move dmi_available declaration to linux/dmi.h ACPI: processor: Fix null pointer dereference in throttling
-
Mel Gorman authored
Partial revert the changes made by 04231b30 to the kmem_list3 management. On a machine with a memoryless node, this BUG_ON was triggering static void *____cache_alloc_node(struct kmem_cache *cachep, gfp_t flags, int nodeid) { struct list_head *entry; struct slab *slabp; struct kmem_list3 *l3; void *obj; int x; l3 = cachep->nodelists[nodeid]; BUG_ON(!l3); Signed-off-by:
Mel Gorman <mel@csn.ul.ie> Cc: Pekka Enberg <penberg@cs.helsinki.fi> Acked-by:
Christoph Lameter <clameter@sgi.com> Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> Cc: Nishanth Aravamudan <nacc@us.ibm.com> Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Cc: Paul Mackerras <paulus@samba.org> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Larry Woodman authored
The shared page table code for hugetlb memory on x86 and x86_64 is causing a leak. When a user of hugepages exits using this code the system leaks some of the hugepages. ------------------------------------------------------- Part of /proc/meminfo just before database startup: HugePages_Total: 5500 HugePages_Free: 5500 HugePages_Rsvd: 0 Hugepagesize: 2048 kB Just before shutdown: HugePages_Total: 5500 HugePages_Free: 4475 HugePages_Rsvd: 0 Hugepagesize: 2048 kB After shutdown: HugePages_Total: 5500 HugePages_Free: 4988 HugePages_Rsvd: 0 Hugepagesize: 2048 kB ---------------------------------------------------------- The problem occurs durring a fork, in copy_hugetlb_page_range(). It locates the dst_pte using huge_pte_alloc(). Since huge_pte_alloc() calls huge_pmd_share() it will share the pmd page if can, yet the main loop in copy_hugetlb_page_range() does a get_page() on every hugepage. This is a violation of the shared hugepmd pagetable protocol and creates additional referenced to the hugepages causing a leak when the unmap of the VMA occurs. We can skip the entire replication of the ptes when the hugepage pagetables are shared. The attached patch skips copying the ptes and the get_page() calls if the hugetlbpage pagetable is shared. [akpm@linux-foundation.org: coding-style cleanups] Signed-off-by:
Larry Woodman <lwoodman@redhat.com> Signed-off-by:
Adam Litke <agl@us.ibm.com> Cc: Badari Pulavarty <pbadari@us.ibm.com> Cc: Ken Chen <kenchen@google.com> Cc: David Gibson <david@gibson.dropbear.id.au> Cc: William Lee Irwin III <wli@holomorphy.com> Signed-off-by:
-
Eric W. Biederman authored
: Stefan Roese <sr@denx.de> said: > ppc: 4xx: sysctl table check failed: /kernel/l2cr .1.31 Missing strategy > > I'm seeing this error message when booting an recent arch/ppc kernel on > 4xx platforms (tested on Ocotea and other 4xx platforms). Booting NFS > rootfs still works fine, but this message kind of makes me "nervous". > This is not seen on 4xx arch/powerpc platforms. Here the bootlog: Because the data field was never filled and a binary sysctl handler was never written this sysctl has never been usable through the sys_sysctl interface. So just remove the binary sysctl number. Making the kernel sanity checks happy. Signed-off-by:
Eric W. Biederman <ebiederm@xmission.com> Reported-by:
Stefan Roese <sr@denx.de> Cc: Josh Boyer <jwboyer@gmail.com> Cc: Wolfgang Denk <wd@denx.de> Cc: Paul Mackerras <paulus@samba.org> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Arjan van de Ven authored
Michael Wu noticed in his lkml post at http://marc.info/?l=linux-kernel&m=119396182726091&w=2 that certain wireless drivers ended up having their name in module memory, which would then crash the kernel on module unload. The patch he proposed was a bit clumsy in that it increased the size of a lockdep entry significantly; the patch below tries another approach, it checks, on module teardown, if the name of a class is in module space and then zaps the class. This is very similar to what we already do with keys that are in module space. Signed-off-by:Arjan van de Ven <arjan@linux.intel.com> Signed-off-by:
Ingo Molnar <mingo@elte.hu> Acked-by:
Peter Zijlstra <a.p.zijlstra@chello.nl> Signed-off-by:
-
David S. Miller authored
This partially reverts 872e2be7 (Constify function pointer tables.) The solaris/socksys.c transformation wasn't valid: arch/sparc64/solaris/socksys.c:192: error: assignment of read-only variable ‘socksys_file_ops’ arch/sparc64/solaris/socksys.c:195: error: assignment of read-only variable ‘socksys_file_ops’ arch/sparc64/solaris/socksys.c:196: error: assignment of read-only variable ‘socksys_file_ops’ Signed-off-by:
David S. Miller <davem@davemloft.net>
-
Len Brown authored
-
Len Brown authored
-
Len Brown authored
-
Len Brown authored
-
Len Brown authored
This reverts commit 93ad7c07. http://bugzilla.kernel.org/show_bug.cgi?id=9798Signed-off-by:
Len Brown <len.brown@intel.com>
-
