All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Only show RESOURCES_64BIT on relevant architectures
Date: Mon, 29 Oct 2007 11:21:52 -0400	[thread overview]
Message-ID: <20071029152152.GD23138@fattire.cabal.ca> (raw)
In-Reply-To: <20071029081010.GA32160@flint.arm.linux.org.uk>

On Mon, Oct 29, 2007 at 08:10:10AM +0000, Russell King wrote:
> On Sun, Oct 28, 2007 at 04:15:49PM -0400, Kyle McMartin wrote:
> > To quote lolcats: CONFIG_RESOURCES_64BIT DO NOT WANT!
> > 
> > I *think* I have the logic of this right... Anyway, I was annoyed by
> > having to do the bloody ugly casts to unsigned long long in
> > arch-specific code. As near as I can tell, we only want this selectable
> > in the case of PAE on x86, and some random PPC and MIPS embedded boards.
> 
> May I suggest trying:
> 
> $ grep RESOURCES_64BIT=y arch/*/configs/* arch/*/defconfig
> 
> to locate those architectures which use this?
> 
> FYI, that grep says ARM, ia64, mips, parisc, powerpc, PPC, s390, sparc64,
> and x86 use this feature.
> 

It would be nice if the people who actually needed it would have
select-ed it. That's how I built the list.

Most of the other examples you listed are obviously 64bit... there should be
more occurances, but I guess they've (alpha, for instance) not updated
their defconfig in a dogs age.

Anyway, sorry I didn't notice ARM. I'll add it to the list on the next
round.

Regards,
	Kyle
(but seriously, this should be select-ed, not just set in a defconfig
 somewhere...)

  reply	other threads:[~2007-10-29 15:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-28 20:15 [PATCH] Only show RESOURCES_64BIT on relevant architectures Kyle McMartin
2007-10-29  1:09 ` David Miller
2007-10-29 15:11   ` Kyle McMartin
2007-10-29  8:10 ` Russell King
2007-10-29 15:21   ` Kyle McMartin [this message]
2007-10-29 15:50     ` Russell King
2007-10-30  2:48 ` Ralf Baechle
2007-10-30  3:03   ` Kumar Gala
2007-10-30  8:37     ` Matthew Wilcox
2007-10-30 11:42       ` Ralf Baechle
2007-10-30 12:13         ` Matthew Wilcox
2007-10-30 14:14           ` Ralf Baechle
2007-10-30 20:00           ` Russell King
2007-10-30 14:19       ` Kumar Gala

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=20071029152152.GD23138@fattire.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=linux-arch@vger.kernel.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 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.