From: Jan Kara <jack@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Cleanup quota header files
Date: Mon, 2 Jun 2008 19:11:05 +0200 [thread overview]
Message-ID: <12124266712214-git-send-email-jack@suse.cz> (raw)
In-Reply-To: y
The series of patches below cleans up quota header files. It does several
things:
1) Rename functions from uppercase to lowercase (compatibility macros
introduced)
2) Remove some unnecessary definitions
3) Split quota.h into two files so that we can properly declare inline
functions.
4) Change macros to inline functions.
So far no filesystem is converted from old function names to new ones -
that is an independent step and I'll hopefully get to that later :).
Andrew, would you merge this series?
Honza
next reply other threads:[~2008-06-02 17:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 17:11 Jan Kara [this message]
2008-06-02 17:11 ` [PATCH] quota: Rename quota functions from upper case, make bigger ones non-inline Jan Kara
2008-06-02 17:11 ` [PATCH] quota: Remove use of info_any_dirty() Jan Kara
2008-06-02 17:11 ` [PATCH] ext4: Add explicit include of <linux/quota.h> into ext4_jbd2.h Jan Kara
2008-06-02 17:11 ` [PATCH] ext2: Add explicit include of <linux/quota.h> into super.c Jan Kara
2008-06-02 17:11 ` [PATCH] quota: Split out quota_struct.h out of quota.h Jan Kara
2008-06-02 17:11 ` [PATCH] quota: Convert macros to inline functions Jan Kara
2008-06-04 13:56 ` [PATCH] quota: Split out quota_struct.h out of quota.h Adrian Bunk
2008-06-04 14:51 ` Jan Kara
2008-06-04 15:26 ` Adrian Bunk
2008-06-04 15:38 ` David Woodhouse
2008-06-04 17:57 ` Jan Kara
2008-06-02 17:41 ` [PATCH] quota: Remove use of info_any_dirty() Vegard Nossum
2008-06-03 9:03 ` Jan Kara
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=12124266712214-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.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