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
46f288a0
Commit
46f288a0
authored
Jun 15, 2009
by
Mike Frysinger
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Blackfin: only build show_interrupts() when procfs is enabled
Signed-off-by:
Mike Frysinger
<
vapier@gentoo.org
>
parent
26579216
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
0 deletions
+2
-0
arch/blackfin/kernel/irqchip.c
arch/blackfin/kernel/irqchip.c
+2
-0
No files found.
arch/blackfin/kernel/irqchip.c
View file @
46f288a0
...
@@ -54,6 +54,7 @@ static struct irq_desc bad_irq_desc = {
...
@@ -54,6 +54,7 @@ static struct irq_desc bad_irq_desc = {
#error "Blackfin architecture does not support CONFIG_CPUMASK_OFFSTACK."
#error "Blackfin architecture does not support CONFIG_CPUMASK_OFFSTACK."
#endif
#endif
#ifdef CONFIG_PROC_FS
int
show_interrupts
(
struct
seq_file
*
p
,
void
*
v
)
int
show_interrupts
(
struct
seq_file
*
p
,
void
*
v
)
{
{
int
i
=
*
(
loff_t
*
)
v
,
j
;
int
i
=
*
(
loff_t
*
)
v
,
j
;
...
@@ -85,6 +86,7 @@ int show_interrupts(struct seq_file *p, void *v)
...
@@ -85,6 +86,7 @@ int show_interrupts(struct seq_file *p, void *v)
}
}
return
0
;
return
0
;
}
}
#endif
/*
/*
* do_IRQ handles all hardware IRQs. Decoded IRQs should not
* do_IRQ handles all hardware IRQs. Decoded IRQs should not
...
...
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