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
450f2757
Commit
450f2757
authored
Jun 03, 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 drivers/ide/pci/hp2366.c
parent
f9bbcb6f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
drivers/ide/pci/hpt366.c
drivers/ide/pci/hpt366.c
+2
-2
No files found.
drivers/ide/pci/hpt366.c
View file @
450f2757
...
...
@@ -1100,7 +1100,7 @@ static void __init init_setup_hpt374 (struct pci_dev *dev, ide_pci_device_t *d)
if
(
PCI_FUNC
(
dev
->
devfn
)
&
1
)
return
;
pci_for_each_dev
(
findev
)
{
while
((
findev
=
pci_find_device
(
PCI_ANY_ID
,
PCI_ANY_ID
,
findev
))
!=
NULL
)
{
if
((
findev
->
vendor
==
dev
->
vendor
)
&&
(
findev
->
device
==
dev
->
device
)
&&
((
findev
->
devfn
-
dev
->
devfn
)
==
1
)
&&
...
...
@@ -1150,7 +1150,7 @@ static void __init init_setup_hpt366 (struct pci_dev *dev, ide_pci_device_t *d)
d
->
channels
=
1
;
pci_read_config_byte
(
dev
,
PCI_INTERRUPT_PIN
,
&
pin1
);
pci_for_each_dev
(
findev
)
{
while
((
findev
=
pci_find_device
(
PCI_ANY_ID
,
PCI_ANY_ID
,
findev
))
!=
NULL
)
{
if
((
findev
->
vendor
==
dev
->
vendor
)
&&
(
findev
->
device
==
dev
->
device
)
&&
((
findev
->
devfn
-
dev
->
devfn
)
==
1
)
&&
...
...
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