From: Joe Thornber <joe@fib011235813.fsnet.co.uk>
To: Greg KH <greg@kroah.com>
Cc: Joe Thornber <joe@fib011235813.fsnet.co.uk>,
lvm-devel@sistina.com, linux-kernel@vger.kernel.org
Subject: Re: dmfs for 2.5.51
Date: Fri, 13 Dec 2002 17:43:55 +0000 [thread overview]
Message-ID: <20021213174355.GA21887@reti> (raw)
In-Reply-To: <20021213172956.GB27800@kroah.com>
On Fri, Dec 13, 2002 at 09:29:56AM -0800, Greg KH wrote:
> The latest for Red Hat 7.2: gcc-2.96-112.7.2
> Are you using 3.2?
gcc version 2.95.4 20011002 (Debian prerelease)
> > The files can be larger than a single page, which complicates things
> > somewhat.
>
> Hm, then using the seq_file interface might be easier. I'll look into
> this.
Remember that the table file needs to hold two files at times: the new
table that is being read in and the old table in case the new table is
invalid.
- Joe
prev parent reply other threads:[~2002-12-13 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 1:26 dmfs for 2.5.51 Greg KH
[not found] ` <3DF93CC9.979CA988@digeo.com>
2002-12-13 5:25 ` Greg KH
2002-12-13 9:58 ` Joe Thornber
2002-12-13 17:32 ` Greg KH
2002-12-13 9:37 ` Joe Thornber
2002-12-13 17:29 ` Greg KH
2002-12-13 17:43 ` Joe Thornber [this message]
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=20021213174355.GA21887@reti \
--to=joe@fib011235813.fsnet.co.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@sistina.com \
/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