From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: eliminate some build warnings
Date: Fri, 12 Feb 2010 16:26:22 -0500 [thread overview]
Message-ID: <20100212212622.GE6084@infradead.org> (raw)
In-Reply-To: <201002122105.o1CL51p4026682@stout.americas.sgi.com>
On Fri, Feb 12, 2010 at 03:05:01PM -0600, Alex Elder wrote:
> A few minor changes to get rid of some build warnings.
> Also a gratuitous name change.
>
> Signed-off-by: Alex Elder <aelder@sgi.com>
Except for the db/check.c hunks these are files shared with the kernel,
and changes should be done to the kernel files first and then resynced.
I've started a resync of the kernel code with libxfs, but it's actually
a lot of work, mostly due to the tracing changes on the kernel side.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-02-12 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 21:05 [PATCH] xfsprogs: eliminate some build warnings Alex Elder
2010-02-12 21:26 ` Christoph Hellwig [this message]
2010-02-12 21:53 ` Alex Elder
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=20100212212622.GE6084@infradead.org \
--to=hch@infradead.org \
--cc=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