From: Christoph Hellwig <hch@infradead.org>
To: Jan Tulak <jtulak@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/2] Prefix LIST_... macros to XFS_LIST_...
Date: Sun, 26 Jul 2015 09:19:20 -0700 [thread overview]
Message-ID: <20150726161920.GB29329@infradead.org> (raw)
In-Reply-To: <1131231186.27908155.1437030777674.JavaMail.zimbra@redhat.com>
libxfs comes form the Linux kernel which uses these names,
so we shouldn't rename them either.
On various BSDS LIST* is used for different list macros, so the real
question is how we end up including those.
Can you post the compiler warnings you see without this patch?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-07-26 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 12:46 [PATCH 0/2] xfsprogs: Partial OS X support Jan Tulak
2015-07-15 12:46 ` [PATCH 1/2] Prefix LIST_... macros to XFS_LIST_ Jan Tulak
2015-07-15 23:53 ` Dave Chinner
2015-07-16 7:12 ` Jan Tulak
2015-07-26 16:19 ` Christoph Hellwig [this message]
2015-07-15 12:46 ` [PATCH 2/2] OS X partial support Jan Tulak
2015-07-16 1:25 ` Dave Chinner
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=20150726161920.GB29329@infradead.org \
--to=hch@infradead.org \
--cc=jtulak@redhat.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