From: "David S. Miller" <davem@davemloft.net>
To: Richard Mortimer <richm@oldelvet.org.uk>
Cc: sparclinux@vger.kernel.org, debian-sparc@lists.debian.org,
linux-lvm@sistina.com, marcelo.tosatti@cyclades.com
Subject: [linux-lvm] Re: [PATCH] Re: lvm problems on sparc64 - Trying to vfree() nonexistent vm area
Date: Wed, 1 Sep 2004 18:37:37 -0700 [thread overview]
Message-ID: <20040901183737.7bf17a39.davem@davemloft.net> (raw)
In-Reply-To: <1093989609.2124.139.camel@duncow>
On Tue, 31 Aug 2004 23:00:10 +0100
Richard Mortimer <richm@oldelvet.org.uk> wrote:
> How do they look
Please resend your patch without all the line breaks
created by your email client. It looks fine otherwise
:)
next prev parent reply other threads:[~2004-09-02 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 0:15 [linux-lvm] lvm problems on sparc64 - Trying to vfree() nonexistent vm area Richard Mortimer
2004-08-31 0:40 ` [linux-lvm] [PATCH] " David S. Miller
2004-08-31 22:00 ` [linux-lvm] " Richard Mortimer
2004-09-02 1:37 ` David S. Miller [this message]
2004-09-02 10:58 ` Richard Mortimer
2004-09-02 20:28 ` David S. Miller
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=20040901183737.7bf17a39.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=debian-sparc@lists.debian.org \
--cc=linux-lvm@redhat.com \
--cc=linux-lvm@sistina.com \
--cc=marcelo.tosatti@cyclades.com \
--cc=richm@oldelvet.org.uk \
--cc=sparclinux@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