On Sun, 30 Jan 2011, Daniel Baluta wrote:
> eventpoll.c has wonderful comments but some annoying typos
> sneaked in:
> * toepoll_ctl -> to epoll_ctl
> * rapresent -> represents
> * sructure -> structure
> * machanism -> mechanism
> * trasfering -> transferring
>
> Signed-off-by: Daniel Baluta <daniel.baluta@xxxxxxxxx>
> ---
> fs/eventpoll.c | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/fs/eventpoll.c b/fs/eventpoll.c
> index cc8a9b7..68bfc0b 100644
> --- a/fs/eventpoll.c
> +++ b/fs/eventpoll.c
> @@ -62,7 +62,7 @@
> * This mutex is acquired by ep_free() during the epoll file
> * cleanup path and it is also acquired by eventpoll_release_file()
> * if a file has been pushed inside an epoll set and it is then
> - * close()d without a previous call toepoll_ctl(EPOLL_CTL_DEL).
> + * close()d without a previous call to epoll_ctl(EPOLL_CTL_DEL).
> * It is possible to drop the "ep->mtx" and to use the global
> * mutex "epmutex" (together with "ep->lock") to have it working,
> * but having "ep->mtx" will make the interface more scalable.
> @@ -145,11 +145,11 @@ struct epitem {
>
> /*
> * This structure is stored inside the "private_data" member of the file
> - * structure and rapresent the main data sructure for the eventpoll
> + * structure and represents the main data structure for the eventpoll
> * interface.
> */
> struct eventpoll {
> - /* Protect the this structure access */
> + /* Protect the access to this structure */
> spinlock_t lock;
>
> /*
> @@ -783,7 +783,7 @@ static struct epitem *ep_find(struct eventpoll *ep, struct file *file, int fd)
>
> /*
> * This is the callback that is passed to the wait queue wakeup
> - * machanism. It is called by the stored file descriptors when they
> + * mechanism. It is called by the stored file descriptors when they
> * have events to report.
> */
> static int ep_poll_callback(wait_queue_t *wait, unsigned mode, int sync, void *key)
> @@ -814,9 +814,9 @@ static int ep_poll_callback(wait_queue_t *wait, unsigned mode, int sync, void *k
> goto out_unlock;
>
> /*
> - * If we are trasfering events to userspace, we can hold no locks
> + * If we are transferring events to userspace, we can hold no locks
> * (because we're accessing user memory, and because of linux f_op->poll()
> - * semantics). All the events that happens during that period of time are
> + * semantics). All the events that happen during that period of time are
> * chained in ep->ovflist and requeued later on.
> */
> if (unlikely(ep->ovflist != EP_UNACTIVE_PTR)) {
Not found in today's linux-next, so I have picked it up.
--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
