From: Holger Schurig <holgerschurig@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 2/7] ARM: uemd: add DEBUG_LL support
Date: Fri, 30 May 2014 08:09:21 +0200 [thread overview]
Message-ID: <CAOpc7mG1WzFvhzctPULHeaZV10uBbVxK1f0kn9qAAiFXkBxc_w@mail.gmail.com> (raw)
In-Reply-To: <1400788130-24202-3-git-send-email-antonynpavlov@gmail.com>
2014-05-22 21:48 GMT+02:00 Antony Pavlov <antonynpavlov@gmail.com>:
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -203,6 +203,7 @@ config ARCH_UEMD
> select OFDEVICE
> select OFTREE
> select CLOCKSOURCE_UEMD
> + select HAS_DEBUG_LL
Why not putting this into the _defconfig?
(On my device, it's neither in defconfig nor in Kconfig, I only had it
on in the initial "bring it to live" period. Afterwards I turned it
off)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-05-30 6:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 19:48 [PATCH v2 0/7] ARM: initial support for RC Module UEMD SoCs and MB 77.07 board Antony Pavlov
2014-05-22 19:48 ` [PATCH v2 1/7] ARM: initial support for RC Module UEMD SoCs Antony Pavlov
2014-05-22 19:48 ` [PATCH v2 2/7] ARM: uemd: add DEBUG_LL support Antony Pavlov
2014-05-30 6:09 ` Holger Schurig [this message]
2014-05-30 9:05 ` Antony Pavlov
2014-05-30 9:03 ` Holger Schurig
2014-05-22 19:48 ` [PATCH v2 3/7] clocksource: add uemd clocksource Antony Pavlov
2014-05-22 19:48 ` [PATCH v2 4/7] ARM: dts: add minimal К1879ХБ1Я devicetree file Antony Pavlov
2014-05-22 19:48 ` [PATCH v2 5/7] ARM: uemd: add mb7707 board support Antony Pavlov
2014-05-22 19:48 ` [PATCH v2 6/7] ARM: uemd: add module-mb7707_defconfig Antony Pavlov
2014-05-22 19:48 ` [PATCH v2 7/7] ARM: mb7707: add barebox mini-howto Antony Pavlov
2014-05-27 5:14 ` [PATCH v2 0/7] ARM: initial support for RC Module UEMD SoCs and MB 77.07 board Sascha Hauer
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=CAOpc7mG1WzFvhzctPULHeaZV10uBbVxK1f0kn9qAAiFXkBxc_w@mail.gmail.com \
--to=holgerschurig@gmail.com \
--cc=antonynpavlov@gmail.com \
--cc=barebox@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