From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 4/4] fsck.gfs2: Make block_mounters static
Date: Wed, 19 Aug 2009 08:49:18 -0400 (EDT) [thread overview]
Message-ID: <988852027.770651250686158504.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <1250670274-7794-5-git-send-email-andy@andrewprice.me.uk>
----- "Andrew Price" <andy@andrewprice.me.uk> wrote:
| Make block_mounters static - it's only used in initialize.c
|
| Signed-off-by: Andrew Price <andy@andrewprice.me.uk>
| ---
| gfs2/fsck/initialize.c | 2 +-
| 1 files changed, 1 insertions(+), 1 deletions(-)
|
| diff --git a/gfs2/fsck/initialize.c b/gfs2/fsck/initialize.c
| index 8bf5782..789895e 100644
| --- a/gfs2/fsck/initialize.c
| +++ b/gfs2/fsck/initialize.c
| @@ -31,7 +31,7 @@
| * Change the lock protocol so nobody can mount the fs
| *
| */
| -int block_mounters(struct gfs2_sbd *sbp, int block_em)
| +static int block_mounters(struct gfs2_sbd *sbp, int block_em)
| {
| if(block_em) {
| /* verify it starts with lock_ */
| --
| 1.6.3.3
Hi,
ACKed by Bob Peterson <rpeterso@redhat.com>
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2009-08-19 12:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 8:24 [Cluster-devel] [PATCH 0/4] gfs2_utils: Trivial patches Andrew Price
2009-08-19 8:24 ` [Cluster-devel] [PATCH 1/4] libgfs2: Fix 'dubious one-bit signed bitfield' sparse errors Andrew Price
2009-08-19 12:34 ` Bob Peterson
2009-08-19 8:24 ` [Cluster-devel] [PATCH 2/4] gfs2_quota: Fix sparse error Andrew Price
2009-08-19 12:35 ` Bob Peterson
2009-08-19 8:24 ` [Cluster-devel] [PATCH 3/4] libgfs2: Fix "Value stored is never read" warnings Andrew Price
2009-08-19 12:47 ` Bob Peterson
2009-08-19 8:24 ` [Cluster-devel] [PATCH 4/4] fsck.gfs2: Make block_mounters static Andrew Price
2009-08-19 12:49 ` Bob Peterson [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=988852027.770651250686158504.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com \
--to=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).