[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110424175212.b67df84c.rdunlap@xenotime.net>
Date: Sun, 24 Apr 2011 17:52:12 -0700
From: Randy Dunlap <rdunlap@...otime.net>
To: Aaron Faanes <dafrito@...il.com>
Cc: John McCutchan <john@...nmccutchan.com>,
Robert Love <rlove@...ve.org>,
Eric Paris <eparis@...isplace.org>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] Documentation: remove some spurious spaces in
inotify.txt
On Sun, 24 Apr 2011 19:35:02 -0500 Aaron Faanes wrote:
> Signed-off-by: Aaron Faanes <dafrito@...il.com>
> ---
> Documentation/filesystems/inotify.txt | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/filesystems/inotify.txt b/Documentation/filesystems/inotify.txt
> index 59a919f..f00c435 100644
> --- a/Documentation/filesystems/inotify.txt
> +++ b/Documentation/filesystems/inotify.txt
> @@ -250,7 +250,7 @@ A: An fd-per-watch quickly consumes more file descriptors than are allowed,
> scales to 1000s of directories, juggling 1000s of fd's just does not seem
> the right interface. It is too heavy.
>
> - Additionally, it _is_ possible to more than one instance and
> + Additionally, it _is_ possible to more than one instance and
Isn't there at least one word missing here?
> juggle more than one queue and thus more than one associated fd. There
> need not be a one-fd-per-process mapping; it is one-fd-per-queue and a
> process can easily want more than one queue.
> --
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists