Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: g4 at novadsp.com <g4@novadsp.com>
To: buildroot@busybox.net
Subject: [Buildroot] Bootchart: Submit a patch questions ...
Date: Fri, 25 Mar 2016 10:53:04 -0000	[thread overview]
Message-ID: <033e01d18684$822e9130$868bb390$@novadsp.com> (raw)
In-Reply-To: <20160324221509.28f24024@free-electrons.com>

Hi Thomas

> > 4. Finally locally BR is configured to get its kernel sources and
> > .config from a local clone of /linux on github. In such a case can BR
> > actually correctly check the dependencies for bootchart? Presumably it
> > does test kernel config settings against the local .config stashed in
build?
> 
> I am not sure to fully understand the question, but if I understand
correctly,
> you're saying that bootchart requires some specific kernel configuration
> options. If that's what you mean, then there are two
> cases:
> 
>  * If the kernel option is needed for bootchart to actually *build*,
>    then you should modify linux/linux.mk to make sure the relevant
>    kernel configurations are enabled when bootchart is enabled.
> 
>  * If the kernel option is only needed for bootchart to work at
>    runtime, then we generally just recommend to indicate which kernel
>    options are needed in the help text of bootchart's Config.in file.

Ideal

> Hope this helps,
> 
> Thomas

It most certainly does. Thanks. I'll tidy things up as per recommendations .

Jerry

      reply	other threads:[~2016-03-25 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 14:59 [Buildroot] Bootchart: Submit a patch questions g4 at novadsp.com
2016-03-24 21:15 ` Thomas Petazzoni
2016-03-25 10:53   ` g4 at novadsp.com [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='033e01d18684$822e9130$868bb390$@novadsp.com' \
    --to=g4@novadsp.com \
    --cc=buildroot@busybox.net \
    /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