Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
linux-davinci
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Redmine
Redmine
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Metrics
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
linux
linux-davinci
Commits
824fcdde
Commit
824fcdde
authored
Apr 25, 2008
by
Paul Mundt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
sh64: Fix up compile warning in event tracer.
Signed-off-by:
Paul Mundt
<
lethal@linux-sh.org
>
parent
ccd80587
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
arch/sh/lib64/dbg.c
arch/sh/lib64/dbg.c
+1
-1
No files found.
arch/sh/lib64/dbg.c
View file @
824fcdde
...
@@ -186,8 +186,8 @@ void evt_debug(int evt, int ret_addr, int event, int tra, struct pt_regs *regs)
...
@@ -186,8 +186,8 @@ void evt_debug(int evt, int ret_addr, int event, int tra, struct pt_regs *regs)
rr
->
pc
=
regs
->
pc
;
rr
->
pc
=
regs
->
pc
;
if
(
sp
<
stack_bottom
+
3092
)
{
if
(
sp
<
stack_bottom
+
3092
)
{
printk
(
"evt_debug : stack underflow report
\n
"
);
int
i
,
j
;
int
i
,
j
;
printk
(
"evt_debug : stack underflow report
\n
"
);
for
(
j
=
0
,
i
=
event_ptr
;
j
<
16
;
j
++
)
{
for
(
j
=
0
,
i
=
event_ptr
;
j
<
16
;
j
++
)
{
rr
=
event_ring
+
i
;
rr
=
event_ring
+
i
;
printk
(
"evt=%08x event=%08x tra=%08x pid=%5d sp=%08lx pc=%08lx
\n
"
,
printk
(
"evt=%08x event=%08x tra=%08x pid=%5d sp=%08lx pc=%08lx
\n
"
,
...
...
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