From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ppc32: Fix sector_t definition with CONFIG_LBD
Date: Mon, 29 Mar 2004 23:18:23 +1000 [thread overview]
Message-ID: <1080566303.1232.32.camel@gaston> (raw)
In-Reply-To: <p7365co848r.fsf@nielsen.suse.de>
>
> -#ifdef CONFIG_LBD
> typedef u64 sector_t;
> #define HAVE_SECTOR_T
> -#endif
Do you need that at all then ? The default unsigned long should
be just fine...
Ben.
next prev parent reply other threads:[~2004-03-29 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 6:32 [PATCH] ppc32: Fix sector_t definition with CONFIG_LBD Benjamin Herrenschmidt
2004-03-29 7:03 ` Andrew Morton
[not found] ` <20040328230351.1a0d0e9c.akpm@osdl.org.suse.lists.linux.kernel>
2004-03-29 8:08 ` Andi Kleen
2004-03-29 9:37 ` [PATCH] small change to fget() Eric Dumazet
2004-03-29 13:18 ` Benjamin Herrenschmidt [this message]
2004-03-29 10:00 ` [PATCH] ppc32: Fix sector_t definition with CONFIG_LBD Andi Kleen
2004-03-29 13:10 ` Anton Blanchard
2004-03-29 13:19 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2004-03-29 19:02 Michel Roelofs
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=1080566303.1232.32.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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