From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm/tegra: add support for tegra30 interrupts
Date: Wed, 2 Nov 2011 19:39:47 +0000 [thread overview]
Message-ID: <20111102193947.GD12913@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111102192625.GD14372@legolas.emea.dhcp.ti.com>
On Wed, Nov 02, 2011 at 09:26:26PM +0200, Felipe Balbi wrote:
> would it be better to just change the default value in
> arm-generic/gpio.h to something very large ?
>
> I mean, ideally that wouldn't be gpio_desc wouldn't be an array anyway
> right ?
You'll excuse me if I take this slightly personally.
You really can't expect me to say that I'm fine with a 6K growth in
kernel size for something that not every platform needs if there's
been objections to maybe a 128 byte growth for including the V:P
patching code in the kernel by default.
Either we care about memory usage or we don't. If we don't, lets get
rid of offering ARM_PATCH_PHYS_VIRT in any configuration and always
build with the dynamic V:P stuff enabled for the trivial cases. I
mean:
config ARM_PATCH_PHYS_VIRT
- bool "Patch physical to virtual translations at runtime" if EMBEDDED
+ bool
default y
depends on !XIP_KERNEL && MMU
depends on !ARCH_REALVIEW || !SPARSEMEM
next prev parent reply other threads:[~2011-11-02 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 15:38 [PATCH] arm/tegra: add support for tegra30 interrupts Peter De Schrijver
2011-11-02 16:39 ` Stephen Warren
2011-11-02 18:06 ` Stephen Warren
2011-11-02 19:09 ` Stephen Warren
2011-11-02 19:21 ` Russell King - ARM Linux
2011-11-02 19:26 ` Felipe Balbi
2011-11-02 19:39 ` Russell King - ARM Linux [this message]
2011-11-02 19:48 ` Felipe Balbi
2011-11-02 19:54 ` Russell King - ARM Linux
2011-11-02 20:40 ` Felipe Balbi
2011-11-02 18:13 ` Colin Cross
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=20111102193947.GD12913@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).