LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ufs: move non-layout parts of ufs_fs.h to fs/ufs/
Date: Sat, 4 Aug 2007 20:36:49 +0100	[thread overview]
Message-ID: <20070804193648.GV21089@ftp.linux.org.uk> (raw)
In-Reply-To: <20070804192431.GA12216@rain>

On Sat, Aug 04, 2007 at 11:24:31PM +0400, Evgeniy Dushistov wrote:
> Move prototypes and in-core structures to fs/ufs/ similar to what most
> other filesystems already do.
> 
> I made little modifications: move also ufs debug macros and
> mount options constants into fs/ufs/ufs.h, this stuff
> also private for ufs.

Is there any reason to have util.h included directly?  Or to have
it as a separate file and not a part of ufs.h, while we are at it...

  reply	other threads:[~2007-08-04 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03 14:09 Christoph Hellwig
2007-08-04 19:24 ` Evgeniy Dushistov
2007-08-04 19:36   ` Al Viro [this message]
2007-08-05 20:11     ` Christoph Hellwig

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=20070804193648.GV21089@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] ufs: move non-layout parts of ufs_fs.h to fs/ufs/' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).