Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
b72b9d44
Commit
b72b9d44
authored
Jun 04, 2003
by
Greg Kroah-Hartman
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[PATCH] PCI: remove usage of pci_for_each_dev() in arch/x86_64/kernel/bluesmoke.c
parent
55fcd1d2
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
arch/x86_64/kernel/bluesmoke.c
arch/x86_64/kernel/bluesmoke.c
+2
-2
No files found.
arch/x86_64/kernel/bluesmoke.c
View file @
b72b9d44
...
@@ -125,9 +125,9 @@ void do_machine_check(struct pt_regs * regs, long error_code)
...
@@ -125,9 +125,9 @@ void do_machine_check(struct pt_regs * regs, long error_code)
static
struct
pci_dev
*
find_k8_nb
(
void
)
static
struct
pci_dev
*
find_k8_nb
(
void
)
{
{
struct
pci_dev
*
dev
;
struct
pci_dev
*
dev
=
NULL
;
int
cpu
=
smp_processor_id
();
int
cpu
=
smp_processor_id
();
pci_for_each_dev
(
dev
)
{
while
((
dev
=
pci_find_device
(
PCI_ANY_ID
,
PCI_ANY_ID
,
dev
))
!=
NULL
)
{
if
(
dev
->
bus
->
number
==
0
&&
PCI_FUNC
(
dev
->
devfn
)
==
3
&&
if
(
dev
->
bus
->
number
==
0
&&
PCI_FUNC
(
dev
->
devfn
)
==
3
&&
PCI_SLOT
(
dev
->
devfn
)
==
(
24U
+
cpu
))
PCI_SLOT
(
dev
->
devfn
)
==
(
24U
+
cpu
))
return
dev
;
return
dev
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment