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
e5233184
Commit
e5233184
authored
Oct 30, 2006
by
Ralf Baechle
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[MIPS] JMR3927: Fixup another victim of the irq pt_regs cleanup.
Signed-off-by:
Ralf Baechle
<
ralf@linux-mips.org
>
parent
77aec999
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
0 deletions
+3
-0
arch/mips/jmr3927/rbhma3100/irq.c
arch/mips/jmr3927/rbhma3100/irq.c
+3
-0
No files found.
arch/mips/jmr3927/rbhma3100/irq.c
View file @
e5233184
...
@@ -288,6 +288,8 @@ static void tx_branch_likely_bug_fixup(void)
...
@@ -288,6 +288,8 @@ static void tx_branch_likely_bug_fixup(void)
static
void
jmr3927_spurious
(
void
)
static
void
jmr3927_spurious
(
void
)
{
{
struct
pt_regs
*
regs
=
get_irq_regs
();
#ifdef CONFIG_TX_BRANCH_LIKELY_BUG_WORKAROUND
#ifdef CONFIG_TX_BRANCH_LIKELY_BUG_WORKAROUND
tx_branch_likely_bug_fixup
();
tx_branch_likely_bug_fixup
();
#endif
#endif
...
@@ -297,6 +299,7 @@ static void jmr3927_spurious(void)
...
@@ -297,6 +299,7 @@ static void jmr3927_spurious(void)
asmlinkage
void
plat_irq_dispatch
(
void
)
asmlinkage
void
plat_irq_dispatch
(
void
)
{
{
struct
pt_regs
*
regs
=
get_irq_regs
();
int
irq
;
int
irq
;
#ifdef CONFIG_TX_BRANCH_LIKELY_BUG_WORKAROUND
#ifdef CONFIG_TX_BRANCH_LIKELY_BUG_WORKAROUND
...
...
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