From: Jens Axboe <axboe@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, jeffpc@optonline.net
Subject: Re: [2.6 patch] *-iosched.c: Use proper documentation path
Date: Tue, 25 Jan 2005 09:06:36 +0100 [thread overview]
Message-ID: <20050125080636.GB2751@suse.de> (raw)
In-Reply-To: <20050125074906.GE3515@stusta.de>
On Tue, Jan 25 2005, Adrian Bunk wrote:
> This patch by Josef "Jeff" Sipek <jeffpc@optonline.net> fixes two
> documentationn paths.
>
> Signed-off-by: Josef "Jeff" Sipek <jeffpc@optonline.net>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Looks fine, thanks.
>
> diff -Nru a/drivers/block/as-iosched.c b/drivers/block/as-iosched.c
> --- a/drivers/block/as-iosched.c 2004-12-02 19:45:45 -05:00
> +++ b/drivers/block/as-iosched.c 2004-12-02 19:45:45 -05:00
> @@ -25,7 +25,7 @@
> #define REQ_ASYNC 0
>
> /*
> - * See Documentation/as-iosched.txt
> + * See Documentation/block/as-iosched.txt
> */
>
> /*
> diff -Nru a/drivers/block/deadline-iosched.c b/drivers/block/deadline-iosched.c
> --- a/drivers/block/deadline-iosched.c 2004-12-02 19:45:45 -05:00
> +++ b/drivers/block/deadline-iosched.c 2004-12-02 19:45:45 -05:00
> @@ -19,7 +19,7 @@
> #include <linux/rbtree.h>
>
> /*
> - * See Documentation/deadline-iosched.txt
> + * See Documentation/block/deadline-iosched.txt
> */
> static int read_expire = HZ / 2; /* max time before a read is submitted. */
> static int write_expire = 5 * HZ; /* ditto for writes, these limits are SOFT! */
>
>
>
>
>
>
--
Jens Axboe
prev parent reply other threads:[~2005-01-25 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 7:49 [2.6 patch] *-iosched.c: Use proper documentation path Adrian Bunk
2005-01-25 8:06 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050125080636.GB2751@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=jeffpc@optonline.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox