[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB=NE6V1JViQyKRdEnaK=Ek4HC4qt_mdyrtk8kT_CG=YkxS+6w@mail.gmail.com>
Date: Mon, 3 Nov 2014 12:21:54 -0800
From: "Luis R. Rodriguez" <mcgrof@...e.com>
To: Johannes Berg <johannes@...solutions.net>
Cc: "backports@...r.kernel.org" <backports@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Yann E. MORIN" <yann.morin.1998@...e.fr>,
Michal Marek <mmarek@...e.cz>,
Stefan Assmann <sassmann@...nic.de>
Subject: Re: [RFC v2 1/4] backports: replace CPTCFG prefix for CONFIG_BACKPORT
On Mon, Nov 3, 2014 at 12:20 PM, Johannes Berg
<johannes@...solutions.net> wrote:
> On Mon, 2014-11-03 at 11:56 -0800, Luis R. Rodriguez wrote:
>
>> With my current code I end up with on a package (not integration):
>>
>> config BACKPORT_BUILD_AVERAGE
>> bool
>> depends on !AVERAGE
>> default y if BACKPORT_USERSEL_BUILD_ALL
>> default y if BACKPORT_AVERAGE
>> #h-file linux/average.h
>> #c-file lib/average.c
>>
>> config BACKPORT_AVERAGE
>> bool
>>
>>
>> I do see I on the package with this on the Makfile though:
>>
>>
>> compat-$(CONFIG_BACKPORT_BACKPORT_BUILD_AVERAGE) += lib-average.o
>>
>> Would it not suffice to just ensure we don't have BACKPORT_BACKPORT_
>> here and just BACKPORT_ once ?
>
> The BACKPORT_BACKPORT_ is actually correct ... but it'll be really hard
> to make sense of :-)
OK I'll prefix the stuff we copy over with something else then, BPAUTO.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists