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
Kirill Smelkov
linux
Commits
4f778e73
Commit
4f778e73
authored
Aug 15, 2003
by
David S. Miller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[IDE]: Use pci_name() in amd74xx driver.
parent
964589c2
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
drivers/ide/pci/amd74xx.c
drivers/ide/pci/amd74xx.c
+2
-2
No files found.
drivers/ide/pci/amd74xx.c
View file @
4f778e73
...
...
@@ -104,7 +104,7 @@ static int amd74xx_get_info(char *buffer, char **addr, off_t offset, int count)
amd_print
(
"----------AMD BusMastering IDE Configuration----------------"
);
amd_print
(
"Driver Version: 2.9"
);
amd_print
(
"South Bridge: %s"
,
bmide_dev
->
dev
.
name
);
amd_print
(
"South Bridge: %s"
,
pci_name
(
bmide_dev
)
);
pci_read_config_byte
(
dev
,
PCI_REVISION_ID
,
&
t
);
amd_print
(
"Revision: IDE %#x"
,
t
);
...
...
@@ -365,7 +365,7 @@ static unsigned int __init init_chipset_amd74xx(struct pci_dev *dev, const char
pci_read_config_byte
(
dev
,
PCI_REVISION_ID
,
&
t
);
printk
(
KERN_INFO
"AMD_IDE: %s (rev %02x) %s controller on pci%s
\n
"
,
dev
->
dev
.
name
,
t
,
amd_dma
[
amd_config
->
flags
&
AMD_UDMA
],
pci_name
(
dev
));
pci_name
(
dev
)
,
t
,
amd_dma
[
amd_config
->
flags
&
AMD_UDMA
],
pci_name
(
dev
));
/*
* Register /proc/ide/amd74xx entry
...
...
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