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
cbf98efd
Commit
cbf98efd
authored
Oct 11, 2002
by
Russell King
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[SERIAL] Fix uart_type compilation error when CONFIG_PROC_FS=n
parent
52a22f80
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
drivers/serial/core.c
drivers/serial/core.c
+2
-2
No files found.
drivers/serial/core.c
View file @
cbf98efd
...
@@ -1604,8 +1604,6 @@ static int uart_open(struct tty_struct *tty, struct file *filp)
...
@@ -1604,8 +1604,6 @@ static int uart_open(struct tty_struct *tty, struct file *filp)
return
retval
;
return
retval
;
}
}
#ifdef CONFIG_PROC_FS
static
const
char
*
uart_type
(
struct
uart_port
*
port
)
static
const
char
*
uart_type
(
struct
uart_port
*
port
)
{
{
const
char
*
str
=
NULL
;
const
char
*
str
=
NULL
;
...
@@ -1619,6 +1617,8 @@ static const char *uart_type(struct uart_port *port)
...
@@ -1619,6 +1617,8 @@ static const char *uart_type(struct uart_port *port)
return
str
;
return
str
;
}
}
#ifdef CONFIG_PROC_FS
static
int
uart_line_info
(
char
*
buf
,
struct
uart_driver
*
drv
,
int
i
)
static
int
uart_line_info
(
char
*
buf
,
struct
uart_driver
*
drv
,
int
i
)
{
{
struct
uart_state
*
state
=
drv
->
state
+
i
;
struct
uart_state
*
state
=
drv
->
state
+
i
;
...
...
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