From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, ak@suse.de,
ralf@linux-mips.org, paulus@samba.org, schwidefsky@de.ibm.com,
lethal@linux-sh.org, kkojima@rr.iij4u.or.jp,
ysato@users.sourceforge.jp
Subject: Re: [PATCH] Handle CONFIG_LBD and CONFIG_LSF in one place
Date: Wed, 26 Apr 2006 23:04:59 -0600 [thread overview]
Message-ID: <20060427050459.GB29147@parisc-linux.org> (raw)
In-Reply-To: <20060426183442.78e40e3b.akpm@osdl.org>
On Wed, Apr 26, 2006 at 06:34:42PM -0700, Andrew Morton wrote:
> Matthew Wilcox <matthew@wil.cx> wrote:
> >
> > CONFIG_LBD and CONFIG_LSF are spread into asm/types.h for no particularly
> > good reason. Centralising the definition in linux/types.h means that arch
> > maintainers don't need to bother adding it, as well as fixing the problem
> > with x86-64 users being asked to make a decision that has absolutely no
> > effect. The H8/300 porters seem particularly confused since I'm not aware
> > of any microcontrollers that need to support 2TB filesystems these days.
>
> x86_64:
>
> include/linux/types.h:137: error: conflicting types for 'sector_t'
> include/asm/types.h:51: error: previous declaration of 'sector_t' was here
is the conflicting patch available somewhere so i can put a patch in for
it? basically, you just need to delete the typedefs for sector_t and
blkcnt_t, just like i've done for the other architectures.
next prev parent reply other threads:[~2006-04-27 5:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 14:05 [PATCH] Handle CONFIG_LBD and CONFIG_LSF in one place Matthew Wilcox
2006-04-27 1:34 ` Andrew Morton
2006-04-27 5:04 ` Matthew Wilcox [this message]
2006-04-27 5:15 ` Andrew Morton
2006-04-27 6:03 ` Matthew Wilcox
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=20060427050459.GB29147@parisc-linux.org \
--to=matthew@wil.cx \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=kkojima@rr.iij4u.or.jp \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@osdl.org \
--cc=ysato@users.sourceforge.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.