linux/drivers/pci/hotplug/ibmphp_res.c, branch v3.8Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
https://git.shady.money/linux/atom?h=v3.82010-02-11T01:45:09Zibmphp: Rename add_range() to add_bus_range() to avoid conflict2010-02-11T01:45:09ZH. Peter Anvinhpa@zytor.com2010-02-11T01:45:09Zurn:sha1:c85e4aae699360e8db4ebfe710e917ac9b6fc77e
Rename add_range() to add_bus_range() to avoid conflict with the
naming of the generic range manipulation functions.
LKML-Reference: <1265793639-15071-4-git-send-email-yinghai@kernel.org>
Cc: Yinghai Lu <yinghai@kernel.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
PCI: replace remaining __FUNCTION__ occurrences2008-04-21T04:47:09ZHarvey Harrisonharvey.harrison@gmail.com2008-03-04T03:09:46Zurn:sha1:66bef8c059015ba2b36bb5759080336feb01e680
__FUNCTION__ is gcc-specific, use __func__
Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
[PATCH] ibmphp: remove TRUE and FALSE2006-03-23T22:35:17ZKristen Accardikristen.c.accardi@intel.com2006-03-15T00:24:47Zurn:sha1:dc6712d1261ee4585771724320d28580888818eb
This patch removes the defines TRUE and FALSE and just uses 0 or 1.
Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
[PATCH] PCI: kzalloc() conversion in drivers/pci2006-03-23T22:35:17ZEric Sesterhennsnakebyte@gmx.de2006-02-28T14:34:49Zurn:sha1:f5afe8064f3087bead8fea7e32547c2a3ada5fd0
this patch converts drivers/pci to kzalloc usage.
Compile tested with allyes config.
Signed-off-by: Eric Sesterhenn <snakebyte@gmx.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Linux-2.6.12-rc22005-04-16T22:20:36ZLinus Torvaldstorvalds@ppc970.osdl.org2005-04-16T22:20:36Zurn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.
Let it rip!