From: Hugh Dickins <hugh@veritas.com>
To: Dmitriy Monakhov <dmonakhov@sw.ru>
Cc: linux-kernel@vger.kernel.org, npiggin@suse.de,
mark.fasheh@oracle.com, linux-ext4@vger.kernel.org
Subject: Re: [patch] new aop loop fix
Date: Wed, 13 Jun 2007 15:48:16 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706131543380.10580@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070613172939.GE13815@localhost.sw.ru>
On Wed, 13 Jun 2007, Dmitriy Monakhov wrote:
> Btw: Nick's patches broke LO_CRYPT_XOR mode,
It would help him if you could describe how.
> but it is ok because
> this feature was absolete and not used by anyone, am i right here?
I know nothing of this; but so long as its code remains in the driver,
I'd say we should be supporting it rather than breaking it.
Hugh
next prev parent reply other threads:[~2007-06-13 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-13 13:46 [patch] new aop loop fix Dmitriy Monakhov
2007-06-13 13:36 ` Hugh Dickins
2007-06-13 17:29 ` Dmitriy Monakhov
2007-06-13 14:48 ` Hugh Dickins [this message]
2007-06-16 15:39 ` [PATCH] deny partial write for loop dev fd Dmitriy Monakhov
2007-06-18 2:39 ` Nick Piggin
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=Pine.LNX.4.64.0706131543380.10580@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=dmonakhov@sw.ru \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=npiggin@suse.de \
/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