From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] arm64: Linux kernel port
Date: Mon, 1 Oct 2012 21:49:51 +0100 [thread overview]
Message-ID: <20121001204950.GA11875@arm.com> (raw)
In-Reply-To: <CA+55aFxefxzYB1iLFfWJeen6XK+5MZEMDjMLJQPS9Satr_5CxA@mail.gmail.com>
On Mon, Oct 01, 2012 at 07:59:52PM +0100, Linus Torvalds wrote:
> On Mon, Oct 1, 2012 at 9:00 AM, Catalin Marinas <catalin.marinas@arm.com> wrote:
> >
> > Please pull the tag below containing the arm64 Linux port. The code
> > lives primarily under arch/arm64/ with a few bits of generic code
> > outside this. Thanks.
>
> Ok, pulled.
Thanks.
> However, looking at the non-arm64 changes, I note:
>
> - the UID16 config option *has* to be fixed.
>
> This is not really about arm64, the ugliness comes from every crazy
> architecture. But we really need to fix this to have something like a
> "HAVE_UID16" config option, and have the architectures that support
> this select that option, so that the UID16 config option can just have
> a "depends on HAVE_UID16".
>
> Please? Anybody?
>
> - same goes for DEBUG_KMEMLEAK and DEBUG_BUGVERBOSE.
>
> - very similar issues for the crazy mess of "#if defined()" in
> kernel/sysctl.c. Can we please just add a SYSCTL_EXCEPTION_TRACE
> config option, and have the architectures that want this just select
> it?
I agree, they don't look nice. I'll post patches to clean them up.
--
Catalin
prev parent reply other threads:[~2012-10-01 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 16:00 [GIT PULL] arm64: Linux kernel port Catalin Marinas
2012-10-01 18:59 ` Linus Torvalds
2012-10-01 20:49 ` Catalin Marinas [this message]
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=20121001204950.GA11875@arm.com \
--to=catalin.marinas@arm.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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