From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfsprogs: libxcmd: support wildcard for fs_table lookups
Date: Wed, 28 Sep 2011 06:44:32 -0500 [thread overview]
Message-ID: <1317210274-13086-1-git-send-email-aelder@sgi.com> (raw)
These two patches add support for the use of 0 as a wildcard value
for indicating the type of entry wanted in a fs_table search. This
allows some code in xfs_quota to be simplified a bit, and (perhaps)
makes it clearer that in most cases searches only look for one type.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-09-28 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 11:44 Alex Elder [this message]
2011-09-28 11:44 ` [PATCH 1/2] xfsprogs: libxcmd: allow 0 as a wildcard fs_table entry type selector Alex Elder
2011-09-28 11:44 ` [PATCH 2/2] xfsprogs: xfs_quota: kill local variable "type" from free_f() Alex Elder
2011-09-29 11:07 ` Christoph Hellwig
2011-09-29 11:06 ` [PATCH 1/2] xfsprogs: libxcmd: allow 0 as a wildcard fs_table entry type selector 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=1317210274-13086-1-git-send-email-aelder@sgi.com \
--to=aelder@sgi.com \
--cc=xfs@oss.sgi.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