mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Quinlan <quinlan@transmeta.com>
To: Johan Adolfsson <johan.adolfsson@axis.com>
Cc: <quinlan@transmeta.com>, <marcelo@conectiva.com.br>,
	<torvalds@transmeta.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cramfs 1/6 - timestamp in includes
Date: Mon, 29 Apr 2002 16:29:14 -0700 (PDT)	[thread overview]
Message-ID: <15565.55114.422518.394576@transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204291326230.25892-100000@ado-2.axis.se>

Johan Adolfsson writes:

> 1. Support for fstime and EDITION_TIMESTAMP in cramfs include files.
>    Uses the edition field in fsid if the CRAMFS_FLAG_EDITION_TIMESTAMP
>    flag is set.
> 2. Support for fstime in fs/cramfs/inode.c together with
>    fixing hardcoded blocksize conversion
>    (Now uses /(PAGE_CACHE_SIZE/1024) instead of >> 2).
> 3. The tools: mkcramfs.c and cramfsck.c: Add support for timestamp in the
>    edition field (fstime) and added the option -b blocksize.
>    For cramfsck.c it also fixes a segfault that occured in the error
>    message if the incorrect blocksize is used (order of arguments wrong).

These first three look good.  I made a few minor changes and merged it
with the big-endian patch, so I'll send you my current version before
sending it onwards to Marcelo and Linus.

The big-endian patch was waiting for 2.4.19 to be released, but maybe I
should just submit it if 2.4.19 is going to be a while.  Also, all of
the big-endian changes are checked into the CVS tree now.

Dan

  reply	other threads:[~2002-04-29 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-29 11:54 Johan Adolfsson
2002-04-29 23:29 ` Daniel Quinlan [this message]
2002-04-30 10:09   ` johan.adolfsson

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=15565.55114.422518.394576@transmeta.com \
    --to=quinlan@transmeta.com \
    --cc=johan.adolfsson@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®