From: Jeff Garzik <jeff@garzik.org>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, akpm@linux-foundation.org, jj@chaosbits.net,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Make CONFIG_SLOW_WORK an automatic rather than manual config option
Date: Mon, 06 Apr 2009 13:03:40 -0400 [thread overview]
Message-ID: <49DA35EC.1000703@garzik.org> (raw)
In-Reply-To: <20090406144725.19407.16817.stgit@warthog.procyon.org.uk>
David Howells wrote:
> Make CONFIG_SLOW_WORK an automatic rather than manual config option so that
> people configuring their kernels don't have to make the choice. It can be
> selected automatically by those things that require it (such as FS-Cache).
>
> Signed-off-by: David Howells <dhowells@redhat.com>
Acked-by: Jeff Garzik <jgarzik@redhat.com>
thanks!
next prev parent reply other threads:[~2009-04-06 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 14:47 [PATCH] Make CONFIG_SLOW_WORK an automatic rather than manual config option David Howells
2009-04-06 17:03 ` Jeff Garzik [this message]
2009-04-06 17:06 ` Kyle McMartin
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=49DA35EC.1000703@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jj@chaosbits.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).