backports.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Bagg <jbagg@lenbrook.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: backports@vger.kernel.org
Subject: Re: Issue reading kernel config
Date: Thu, 08 Aug 2013 07:45:40 -0400	[thread overview]
Message-ID: <520384E4.1010205@lenbrook.com> (raw)
In-Reply-To: <1375943844.8186.0.camel@jlt4.sipsolutions.net>

On 13-08-08 02:37 AM, Johannes Berg wrote:
> On Wed, 2013-08-07 at 16:33 -0400, Jonathan Bagg wrote:
>> So I had a look at the Kconfig file and realised it isn't a kernel
>> config.  If I add
>>
>> config BT
>>       def_bool y
>>
>> under the "# some hacks ..." section, I can enable BT drivers in
>> backports in the menuconfig.  So if a kconfig depends on an external
>> config, there is no way to feed in a kernel config to backports?  you
>> list external config under "# some hacks ..." section?
> The script should create a dummy Kconfig.kernel from your
> kernel's .config, and read that for the dependencies from the kernel.
I'd like to figure out why it isn't working.  Which script reads the 
kernel's .config?

Jon

  reply	other threads:[~2013-08-08 11:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1375338204-2021-8-git-send-email-sujith@msujith.org>
     [not found] ` <1375370826-1387-1-git-send-email-sujith@msujith.org>
     [not found]   ` <51FA8ECD.7070401@lenbrook.com>
2013-08-01 17:47     ` cross compile backports? Solomon Peachy
2013-08-01 19:03       ` Luis R. Rodriguez
2013-08-01 19:36         ` Solomon Peachy
2013-08-01 19:12       ` cross compile backports with LTIB Jonathan Bagg
2013-08-01 19:17         ` Jonathan Bagg
2013-08-07 19:55         ` Issue reading kernel config Jonathan Bagg
2013-08-07 20:33           ` Jonathan Bagg
2013-08-08  6:37             ` Johannes Berg
2013-08-08 11:45               ` Jonathan Bagg [this message]
2013-08-08 12:16                 ` Johannes Berg

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=520384E4.1010205@lenbrook.com \
    --to=jbagg@lenbrook.com \
    --cc=backports@vger.kernel.org \
    --cc=johannes@sipsolutions.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;
as well as URLs for NNTP newsgroup(s).