From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"golf@perches.com" <golf@perches.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Cc: "boris.brezillon@bootlin.com" <boris.brezillon@bootlin.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"joel@jms.id.au" <joel@jms.id.au>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>
Subject: Re: [RESEND PATCH 1/6] ARM: config: multi_v5: enable dynamic debug
Date: Fri, 21 Sep 2018 16:58:29 +0000 [thread overview]
Message-ID: <1537549106.6513.1.camel@toradex.com> (raw)
In-Reply-To: <f20387e3-4cce-78eb-886c-03ab8c39ae42@gmail.com>
On Wed, 2018-08-15 at 18:29 -0700, Florian Fainelli wrote:
>
> On 08/14/2018 07:16 AM, Joe Perches wrote:
> > On Tue, 2018-08-14 at 16:06 +0200, Marcel Ziswiler wrote:
> > > From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> > >
> > > Dynamic debug is really helpful.
> >
> > It's useful, but perhaps not appropriate.
> >
> > Most arm configs are for small resource constrained systems.
>
> Yes, but multi_v*_defconfig, by definition are not, so this really
> seems
> acceptable to me here.
What is the conclusion now? Is anybody gona pull this patchset in? Or
are any changes needed?
> > dynamic_debug adds a lot of additional text and a fair amount of
> > data.
> >
> >
> > > Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> > >
> > > ---
> > >
> > > arch/arm/configs/multi_v5_defconfig | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/arch/arm/configs/multi_v5_defconfig
> > > b/arch/arm/configs/multi_v5_defconfig
> > > index 318b76fa26d1..b302ac68d587 100644
> > > --- a/arch/arm/configs/multi_v5_defconfig
> > > +++ b/arch/arm/configs/multi_v5_defconfig
> > > @@ -275,6 +275,7 @@ CONFIG_NLS_CODEPAGE_850=y
> > > CONFIG_NLS_ISO8859_1=y
> > > CONFIG_NLS_ISO8859_2=y
> > > CONFIG_NLS_UTF8=y
> > > +CONFIG_DYNAMIC_DEBUG=y
> > > CONFIG_DEBUG_INFO=y
> > > CONFIG_DEBUG_FS=y
> > > CONFIG_MAGIC_SYSRQ=y
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-09-21 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 14:06 [RESEND PATCH 1/6] ARM: config: multi_v5: enable dynamic debug Marcel Ziswiler
2018-08-14 14:06 ` [RESEND PATCH 2/6] ARM: multi_v7_defconfig: update order Marcel Ziswiler
2018-08-14 14:06 ` [RESEND PATCH 3/6] ARM: multi_v7_defconfig: enable dynamic debug Marcel Ziswiler
2018-08-14 14:06 ` [RESEND PATCH 4/6] ARM: defconfig: tegra: " Marcel Ziswiler
2018-08-14 14:06 ` [RESEND PATCH 5/6] ARM: multi_v7_defconfig: enable tegra raw nand driver Marcel Ziswiler
2018-08-14 14:06 ` [RESEND PATCH 6/6] ARM: defconfig: tegra: " Marcel Ziswiler
2018-08-14 14:16 ` [RESEND PATCH 1/6] ARM: config: multi_v5: enable dynamic debug Joe Perches
2018-08-16 1:29 ` Florian Fainelli
2018-09-21 16:58 ` Marcel Ziswiler [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=1537549106.6513.1.camel@toradex.com \
--to=marcel.ziswiler@toradex.com \
--cc=andrew@aj.id.au \
--cc=boris.brezillon@bootlin.com \
--cc=f.fainelli@gmail.com \
--cc=golf@perches.com \
--cc=herbert@gondor.apana.org.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).