From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Fengguang Wu <fengguang.wu@intel.com>,
Linux-Arch <linux-arch@vger.kernel.org>,
Linux MIPS Mailing List <linux-mips@linux-mips.org>,
James Hogan <james.hogan@imgtec.com>,
Paul Burton <paul.burton@imgtec.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Michal Marek <mmarek@suse.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE
Date: Fri, 29 Jan 2016 09:01:31 +0100 [thread overview]
Message-ID: <CAMuHMdX33SQe8n7SRda0TjQV05yP1zbuw129Jqjknt8=CY=LjA@mail.gmail.com> (raw)
In-Reply-To: <7619136.niuXthzi6R@wuerfel>
Hi Arnd,
On Fri, Jan 29, 2016 at 12:07 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> The other related issue is the DEBUG_UART_{VIRT,PHYS} setting,
> where there is no safe platform-specific default. I have two
> ideas for working around that, maybe one of them sounds ok to
> you:
>
> a) find a way to warn and/or disable DEBUG_LL when no address
> is set, rather than failing the build
>
> b) add 'default 0 if COMPILE_TEST' to make it harder to get this
> wrong by accident (hopefully nobody tries to run a COMPILE_TEST
> kernel). Also maybe add a #warning if DEBUG_UART_VIRT is
Make sure to add it at the end of the list, so enabling COMPILE_TEST in a
working .config should give another working .config.
Perhaps you can use 0xdeadbeef instead of 0, and add
#if DEBUG_UART_PHYS == 0xdeadbeed
#warning Broken value of DEBUG_UART_PHYS.
#endif
somewhere?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE
Date: Fri, 29 Jan 2016 09:01:31 +0100 [thread overview]
Message-ID: <CAMuHMdX33SQe8n7SRda0TjQV05yP1zbuw129Jqjknt8=CY=LjA@mail.gmail.com> (raw)
In-Reply-To: <7619136.niuXthzi6R@wuerfel>
Hi Arnd,
On Fri, Jan 29, 2016 at 12:07 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> The other related issue is the DEBUG_UART_{VIRT,PHYS} setting,
> where there is no safe platform-specific default. I have two
> ideas for working around that, maybe one of them sounds ok to
> you:
>
> a) find a way to warn and/or disable DEBUG_LL when no address
> is set, rather than failing the build
>
> b) add 'default 0 if COMPILE_TEST' to make it harder to get this
> wrong by accident (hopefully nobody tries to run a COMPILE_TEST
> kernel). Also maybe add a #warning if DEBUG_UART_VIRT is
Make sure to add it at the end of the list, so enabling COMPILE_TEST in a
working .config should give another working .config.
Perhaps you can use 0xdeadbeef instead of 0, and add
#if DEBUG_UART_PHYS == 0xdeadbeed
#warning Broken value of DEBUG_UART_PHYS.
#endif
somewhere?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-01-29 8:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 11:27 [linux-review:James-Hogan/kbuild-Remove-stale-asm-generic-wrappers/20160119-183642] d979f99e9cc14e2667e9b6e268db695977e4197a BUILD DONE kbuild test robot
2016-01-19 11:27 ` kbuild test robot
2016-01-19 11:27 ` kbuild test robot
2016-01-19 14:26 ` Arnd Bergmann
2016-01-26 5:30 ` Fengguang Wu
2016-01-26 5:35 ` Fengguang Wu
2016-01-26 16:27 ` Arnd Bergmann
2016-01-27 8:37 ` Fengguang Wu
2016-01-27 9:11 ` Arnd Bergmann
2016-01-27 9:30 ` Fengguang Wu
2016-01-27 9:44 ` Arnd Bergmann
2016-01-27 9:44 ` Arnd Bergmann
2016-01-28 3:14 ` Fengguang Wu
2016-01-28 3:14 ` Fengguang Wu
2016-01-28 12:07 ` Arnd Bergmann
2016-01-28 12:07 ` Arnd Bergmann
2016-01-28 17:42 ` Russell King - ARM Linux
2016-01-28 17:42 ` Russell King - ARM Linux
2016-01-28 23:07 ` Arnd Bergmann
2016-01-28 23:07 ` Arnd Bergmann
2016-01-29 8:01 ` Geert Uytterhoeven [this message]
2016-01-29 8:01 ` Geert Uytterhoeven
2016-01-29 8:01 ` Geert Uytterhoeven
2016-01-29 20:44 ` Arnd Bergmann
2016-01-29 20:44 ` Arnd Bergmann
2016-01-29 20:44 ` Arnd Bergmann
2016-01-29 21:24 ` Geert Uytterhoeven
2016-01-29 21:24 ` Geert Uytterhoeven
2016-01-29 21:24 ` Geert Uytterhoeven
2016-01-29 21:24 ` Geert Uytterhoeven
2016-01-29 21:54 ` Arnd Bergmann
2016-01-29 21:54 ` Arnd Bergmann
2016-01-29 21:54 ` Arnd Bergmann
2016-01-29 23:15 ` Russell King - ARM Linux
2016-01-29 23:15 ` Russell King - ARM Linux
2016-01-29 23:15 ` Russell King - ARM Linux
2016-01-29 21:46 ` Russell King - ARM Linux
2016-01-29 21:46 ` Russell King - ARM Linux
2016-01-28 18:00 ` Geert Uytterhoeven
2016-01-28 18:00 ` Geert Uytterhoeven
2016-01-28 18:00 ` Geert Uytterhoeven
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='CAMuHMdX33SQe8n7SRda0TjQV05yP1zbuw129Jqjknt8=CY=LjA@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=f.fainelli@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=james.hogan@imgtec.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@arm.linux.org.uk \
--cc=mmarek@suse.com \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=xypron.glpk@gmx.de \
/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.