diff options
| author | Randy Dunlap <randy.dunlap@oracle.com> | 2008-03-23 20:28:20 +0100 |
|---|---|---|
| committer | Jean Delvare <khali@hyperion.delvare> | 2008-03-23 20:28:20 +0100 |
| commit | 8c07e46f39d8c613cf2281c7d87908c0105fb0d0 (patch) | |
| tree | 7802df61b3dadd01fc0f68edc92910c0938d66a1 /drivers/i2c/i2c-core.c | |
| parent | bc80cc55f0a1689b86bf037c9d84cb7ff2b95131 (diff) | |
| download | kernel_samsung_espresso10-8c07e46f39d8c613cf2281c7d87908c0105fb0d0.zip kernel_samsung_espresso10-8c07e46f39d8c613cf2281c7d87908c0105fb0d0.tar.gz kernel_samsung_espresso10-8c07e46f39d8c613cf2281c7d87908c0105fb0d0.tar.bz2 | |
i2c: Fix docbook problem
Sometimes kernel-doc and xmlto conspire to create output that is invalid
and causes problems. Until I know a real/better solution, change the
source code that causes this.
If anyone has better fixes or can just explain what is happening here,
that would be great.
xmlto: input does not validate (status 1)
mmotm-2008-0314-1449/Documentation/DocBook/kernel-api.xml:71468: parser error : Opening and ending tag mismatch: programlisting line 71464 and para
</para><para>
^
mmotm-2008-0314-1449/Documentation/DocBook/kernel-api.xml:71480: parser error : Opening and ending tag mismatch: para line 71473 and programlisting
</programlisting></informalexample>
^
make[1]: *** [Documentation/DocBook/kernel-api.html] Error 1
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Jean Delvare <khali@linux-fr.org>
Diffstat (limited to 'drivers/i2c/i2c-core.c')
| -rw-r--r-- | drivers/i2c/i2c-core.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c index fd84b2a..8b645c6 100644 --- a/drivers/i2c/i2c-core.c +++ b/drivers/i2c/i2c-core.c @@ -489,8 +489,8 @@ EXPORT_SYMBOL(i2c_add_adapter); * Context: can sleep * * This routine is used to declare an I2C adapter when its bus number - * matters. Example: for I2C adapters from system-on-chip CPUs, or - * otherwise built in to the system's mainboard, and where i2c_board_info + * matters. For example, use it for I2C adapters from system-on-chip CPUs, + * or otherwise built in to the system's mainboard, and where i2c_board_info * is used to properly configure I2C devices. * * If no devices have pre-been declared for this bus, then be sure to |