Linux backports project
 help / color / mirror / Atom feed
From: Stefan Assmann <sassmann@kpanic.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
	"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
	Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: problem with enabling config options
Date: Thu, 07 May 2015 14:19:57 +0200	[thread overview]
Message-ID: <554B586D.8070805@kpanic.de> (raw)
In-Reply-To: <1430999320.11214.0.camel@sipsolutions.net>

On 07.05.2015 13:48, Johannes Berg wrote:
> On Thu, 2015-05-07 at 13:15 +0200, Stefan Assmann wrote:
>> I'm looking into enabling more wired network drivers and ran into the
>> issue that I could not enable CONFIG_E1000 for example. The problem
>> seems to be that because CONFIG_E100 is disabled you cannot enable
>> anything CONFIG_E100*. It looks like a bug in gentree.py, but my python
>> foo didn't suffice to get it sorted out. Problem should be located
>> somewhere around line 1060 where the CONFIG variable regex stuff
>> happens.
> 
> I think you can try to add \W to the very end of the regex there.
> 
> johannes
> 

Thanks Johannes, that worked. Proposing patch and Cc Hauke.

  Stefan

>From da662be25373468dac47234f2f164fcc8503ebb4 Mon Sep 17 00:00:00 2001
From: Stefan Assmann <sassmann@kpanic.de>
Date: Thu, 7 May 2015 14:08:56 +0200
Subject: [PATCH] backports: fix incorrect disabling of CONFIG options

gentree.py incorrectly disabled CONFIG options that share part of the
name with another already disabled CONFIG option.
For example if CONFIG_E100 was disabled you no longer could enable
CONFIG_E1000 or CONFIG_E1000E.

Signed-off-by: Stefan Assmann <sassmann@kpanic.de>
---
 gentree.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gentree.py b/gentree.py
index edff138..636ea60 100755
--- a/gentree.py
+++ b/gentree.py
@@ -1057,7 +1057,7 @@ def process(kerneldir, copy_list_file, git_revision=None,
     # groups -- 50 seemed safer and is still fast)
     regexes = []
     for some_symbols in [disable_makefile[i:i + 50] for i in range(0, len(disable_makefile), 50)]:
-        r = '^([^#].*((' + bpid.full_prefix_resafe + '|CONFIG_)(' + '|'.join([s for s in some_symbols]) + ')))'
+        r = '^([^#].*((' + bpid.full_prefix_resafe + '|CONFIG_)(' + '|'.join([s for s in some_symbols]) + ')))\W'
         regexes.append(re.compile(r, re.MULTILINE))
     for f in maketree.get_makefiles():
         data = open(f, 'r').read()
-- 
2.1.0


  reply	other threads:[~2015-05-07 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 11:15 problem with enabling config options Stefan Assmann
2015-05-07 11:48 ` Johannes Berg
2015-05-07 12:19   ` Stefan Assmann [this message]
2015-05-11 21:57     ` Hauke Mehrtens

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=554B586D.8070805@kpanic.de \
    --to=sassmann@kpanic.de \
    --cc=backports@vger.kernel.org \
    --cc=hauke@hauke-m.de \
    --cc=johannes@sipsolutions.net \
    --cc=mcgrof@do-not-panic.com \
    /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