public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Valdis.Kletnieks@vt.edu
Cc: themel@iwoars.net, linux-kernel@vger.kernel.org
Subject: Re: Device-backed loop broken in 2.6.0-test2?
Date: Thu, 7 Aug 2003 09:29:13 -0700	[thread overview]
Message-ID: <20030807092913.6db267f1.akpm@osdl.org> (raw)
In-Reply-To: <200308071607.h77G7WPp005392@turing-police.cc.vt.edu>

Valdis.Kletnieks@vt.edu wrote:
>
> /Valdis (who is off to apply the patch that Andrew attached, which doesn't appear to
>  be in -mm5)...

mm5 fixed it differently.


  parent reply	other threads:[~2003-08-07 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 22:40 Device-backed loop broken in 2.6.0-test2? Thomas Themel
2003-08-07  0:40 ` Andrew Morton
2003-08-07  7:23   ` Thomas Themel
2003-08-07 16:07   ` Valdis.Kletnieks
2003-08-07 16:24     ` Valdis.Kletnieks
2003-08-07 16:29     ` Andrew Morton [this message]
2003-08-09 20:48   ` cryptoloop data corruption (was Re: Device-backed loop broken in 2.6.0-test2?) Thomas Themel

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=20030807092913.6db267f1.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=themel@iwoars.net \
    /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