'\" t
.\"     Title: driver_register
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\"      Date: January 2017
.\"    Manual: Device drivers infrastructure
.\"    Source: Kernel Hackers Manual 4.8.15
.\"  Language: English
.\"
.TH "DRIVER_REGISTER" "9" "January 2017" "Kernel Hackers Manual 4\&.8\&." "Device drivers infrastructure"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
driver_register \- register driver with bus
.SH "SYNOPSIS"
.HP \w'int\ driver_register('u
.BI "int driver_register(struct\ device_driver\ *\ " "drv" ");"
.SH "ARGUMENTS"
.PP
\fIdrv\fR
.RS 4
driver to register
.RE
.SH "DESCRIPTION"
.PP
We pass off most of the work to the
\fBbus_add_driver\fR
call, since most of the things we have to do deal with the bus structures\&.
.SH "COPYRIGHT"
.br