Wrap filenames in <filename>.

PR:		docs/34916
Submitted by:	Ceri <setantae@submonkey.net>
This commit is contained in:
Giorgos Keramidas 2002-02-16 23:14:05 +00:00
parent 50ce76a93c
commit ab6fd7a72e
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=12214
2 changed files with 4 additions and 4 deletions
en_US.ISO8859-1/books
arch-handbook/isa
developers-handbook/isa

View file

@ -375,8 +375,8 @@
accessing the configuration resources directly with functions accessing the configuration resources directly with functions
of families <function>resource_query_*()</function> and of families <function>resource_query_*()</function> and
<function>resource_*_value()</function>. Their implementations <function>resource_*_value()</function>. Their implementations
are located in kern/subr_bus.h. The old IDE disk driver are located in <filename>kern/subr_bus.h</filename>. The old IDE disk driver
i386/isa/wd.c contains examples of such use. But the standard <filename>i386/isa/wd.c</filename> contains examples of such use. But the standard
means of configuration must always be preferred. Leave parsing means of configuration must always be preferred. Leave parsing
the configuration resources to the bus configuration the configuration resources to the bus configuration
code.</para> code.</para>

View file

@ -375,8 +375,8 @@
accessing the configuration resources directly with functions accessing the configuration resources directly with functions
of families <function>resource_query_*()</function> and of families <function>resource_query_*()</function> and
<function>resource_*_value()</function>. Their implementations <function>resource_*_value()</function>. Their implementations
are located in kern/subr_bus.h. The old IDE disk driver are located in <filename>kern/subr_bus.h</filename>. The old IDE disk driver
i386/isa/wd.c contains examples of such use. But the standard <filename>i386/isa/wd.c</filename> contains examples of such use. But the standard
means of configuration must always be preferred. Leave parsing means of configuration must always be preferred. Leave parsing
the configuration resources to the bus configuration the configuration resources to the bus configuration
code.</para> code.</para>