All of lore.kernel.org
 help / color / mirror / Atom feed
From: Prabhakar Kushwaha <prabhakar@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] config.mk:Update DBGFLAGS with dwarf information
Date: Mon, 25 Jun 2012 13:10:30 +0530	[thread overview]
Message-ID: <4FE815EE.1060807@freescale.com> (raw)
In-Reply-To: <20120625072104.439C3202239@gemini.denx.de>

Thanks Wolfgang for the reply.

Please find my reply in-lined


On 06/25/2012 12:51 PM, Wolfgang Denk wrote:
> Dear Prabhakar Kushwaha,
>
> In message <4FE7EFA1.2050208@freescale.com> you wrote:
>> Please help me in closing review related comments on this patch.
> It appears most people here on the mailing list see not much need for
> changing the debug flags, probbaly because nobody is using the single
> tool that seems to need the additional flags.

Yes.. it looks like the same :(

> Maybe instead of adding this to the mainline source tree you can
> configure your debug tool to provide these settings on the make
> command line, overwriting the default settings?
>

I will definitely check this point in debug tool.
Or
may be I put debug option somewhere else, other than top level config.mk.

Regards,
Prabhakar

  reply	other threads:[~2012-06-25  7:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-15  8:55 [U-Boot] [PATCH] config.mk:Update DBGFLAGS with dwarf information Prabhakar Kushwaha
2012-04-25  4:11 ` Prabhakar Kushwaha
2012-05-24  4:43   ` Prabhakar Kushwaha
2012-05-24  4:47     ` Graeme Russ
     [not found]     ` <4FE00741.4040202@freescale.com>
2012-06-19  5:08       ` Prabhakar Kushwaha
2012-06-25  4:57         ` Prabhakar Kushwaha
2012-06-25  5:03           ` Graeme Russ
2012-06-25  7:21           ` Wolfgang Denk
2012-06-25  7:40             ` Prabhakar Kushwaha [this message]
2012-05-14  5:53 ` Mike Frysinger
2012-10-15 23:13 ` [U-Boot] " Tom Rini

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=4FE815EE.1060807@freescale.com \
    --to=prabhakar@freescale.com \
    --cc=u-boot@lists.denx.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.