typo fixes

------------

   The kernel provides an interface to manage DMA transfers

   using the DMA channels in the cpu, so that the central

   using the DMA channels in the CPU, so that the central

   duty of managing channel mappings, and programming the

   channel generators is in one place.

   channels to all sources, which means that some devices

   have a restricted number of channels that can be used.

   To allow flexibilty for each cpu type and board, the

   dma code can be given an dma ordering structure which

   To allow flexibility for each CPU type and board, the

   DMA code can be given a DMA ordering structure which

   allows the order of channel search to be specified, as

   well as allowing the prohibition of certain claims.

   struct s3c24xx_dma_order has a list of channels, and

   each channel within has a slot for a list of dma

   channel numbers. The slots are searched in order, for

   the presence of a dma channel number with DMA_CH_VALID

   orred in.

   each channel within has a slot for a list of DMA

   channel numbers. The slots are searched in order for

   the presence of a DMA channel number with DMA_CH_VALID

   or-ed in.

   If the order has the flag DMA_CH_NEVER set, then after

   checking the channel list, the system will return no

   found channel, thus denying the request.

   A board support file can call s3c24xx_dma_order_set()

   to register an complete ordering set. The routine will

   copy the data, so the original can be discared with

   to register a complete ordering set. The routine will

   copy the data, so the original can be discarded with

   __initdata.

136-143 char	Unix98 PTY slaves

		  0 = /dev/pts/0	First Unix98 pseudo-TTY

		  1 = /dev/pts/1	Second Unix98 pesudo-TTY

		  1 = /dev/pts/1	Second Unix98 pseudo-TTY

		    ...

		These device nodes are automatically generated with

For one reason or another, low level drivers don't receive as much

attention or testing as core code, and bugs on driver detach or

initilaization failure doesn't happen often enough to be noticeable.

initialization failure don't happen often enough to be noticeable.

Init failure path is worse because it's much less travelled while

needs to handle multiple entry points.

  devres_release_group(dev, NULL);

  return err_code;

As resource acquision failure usually means probe failure, constructs

As resource acquisition failure usually means probe failure, constructs

like above are usually useful in midlayer driver (e.g. libata core

layer) where interface function shouldn't have side effect on failure.

For LLDs, just returning error code suffices in most cases.

Deferred IO is a way to delay and repurpose IO. It uses host memory as a

buffer and the MMU pagefault as a pretrigger for when to perform the device

IO. The following example may be a useful explaination of how one such setup

IO. The following example may be a useful explanation of how one such setup

works:

- userspace app like Xfbdev mmaps framebuffer

For some types of nonvolatile high latency displays, the desired image is

the final image rather than the intermediate stages which is why it's okay

to not update for each write that is occuring.

to not update for each write that is occurring.

It may be the case that this is useful in other scenarios as well. Paul Mundt

has mentioned a case where it is beneficial to use the page count to decide

  aname=name	aname specifies the file tree to access when the server is

  		offering several exported file systems.

  cache=mode	specifies a cacheing policy.  By default, no caches are used.

  cache=mode	specifies a caching policy.  By default, no caches are used.

			loose = no attempts are made at consistency,

                                intended for exclusive, read-only mounts