From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@lst.de>
Cc: tes@melbourne.sgi.com, xfs@oss.sgi.com
Subject: Re: HAVE_FORMAT32 never enabled in mainline
Date: Sat, 17 Mar 2007 17:00:47 -0500 [thread overview]
Message-ID: <45FC650F.70208@sandeen.net> (raw)
In-Reply-To: <20070317154028.GA18997@lst.de>
Christoph Hellwig wrote:
> Looks like the code for dealing with x86/amd64 logs is never actually
> enable in mainline because nothing defines HAVE_FORMAT32.
Actually since it's all #ifndef (note the n) everything under the
#ifndefs -is- enabled (since it's never defined), so I think it's all
functional.... structures under the #ifndefs are used outside the
#ifndefs, so the #ifndefs can probably just be removed...?
-Eric
next prev parent reply other threads:[~2007-03-17 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 15:40 HAVE_FORMAT32 never enabled in mainline Christoph Hellwig
2007-03-17 22:00 ` Eric Sandeen [this message]
2007-03-19 1:05 ` Timothy Shimmin
2007-03-19 1:04 ` Timothy Shimmin
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=45FC650F.70208@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@lst.de \
--cc=tes@melbourne.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