From: Chris Mason <mason@suse.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lockfs patch for 2.6
Date: Fri, 26 Mar 2004 08:28:14 -0500 [thread overview]
Message-ID: <1080307694.2820.81.camel@watt.suse.com> (raw)
In-Reply-To: <20040326102549.A4248@infradead.org>
On Fri, 2004-03-26 at 05:25, Christoph Hellwig wrote:
> On Sun, Mar 14, 2004 at 10:23:31AM -0500, Chris Mason wrote:
> > > P.S. this patch now kills 16 lines of kernel code summarized :)
> > >
> >
> > It looks good, I'll give it a try.
>
> ping? I've seen you merged the old patch into the suse tree, and having
> shipping distros with incompatible APIs doesn't sound exactly like a good
> idea..
I'm replacing the old one in the suse tree, I just got sucked into to a
few critical tasks. Yours is the way to go.
-chris
next prev parent reply other threads:[~2004-03-26 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 21:31 [PATCH] lockfs patch for 2.6 Chris Mason
2004-03-12 9:31 ` Christoph Hellwig
2004-03-12 15:50 ` Chris Mason
2004-03-12 15:51 ` Christoph Hellwig
2004-03-13 13:14 ` Christoph Hellwig
2004-03-13 15:20 ` Chris Mason
2004-03-13 16:33 ` Christoph Hellwig
2004-03-14 14:00 ` Christoph Hellwig
2004-03-14 15:23 ` Chris Mason
2004-03-26 10:25 ` Christoph Hellwig
2004-03-26 13:28 ` Chris Mason [this message]
2004-04-01 20:35 ` Chris Mason
2004-04-01 22:32 ` Kevin Corry
2004-04-02 20:00 ` Kevin Corry
2004-04-02 20:02 ` Christoph Hellwig
2004-04-02 20:26 ` Kevin Corry
2004-03-14 18:44 ` Andrew Morton
2004-03-14 18:52 ` Christoph Hellwig
2004-03-14 18:56 ` Chris Mason
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=1080307694.2820.81.camel@watt.suse.com \
--to=mason@suse.com \
--cc=hch@infradead.org \
--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