From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Yann E. MORIN" <yann.morin.1998@free.fr>,
Michal Marek <mmarek@suse.cz>,
Stefan Assmann <sassmann@kpanic.de>
Subject: Re: [RFC v2 1/4] backports: replace CPTCFG prefix for CONFIG_BACKPORT
Date: Mon, 03 Nov 2014 21:20:29 +0100 [thread overview]
Message-ID: <1415046029.2726.6.camel@sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6XWWcmRb-3r28obFmChzW1mnynG0LkVDr2-y+QVpq=y9Q@mail.gmail.com> (sfid-20141103_205706_499759_FE8EC472)
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 :-)
johannes
next prev parent reply other threads:[~2014-11-03 20:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 8:21 [RFC v2 0/4] backports: kernel integration support Luis R. Rodriguez
2014-10-29 8:21 ` [RFC v2 1/4] backports: replace CPTCFG prefix for CONFIG_BACKPORT Luis R. Rodriguez
2014-10-31 7:41 ` Johannes Berg
2014-10-31 19:34 ` Luis R. Rodriguez
2014-10-31 20:22 ` Johannes Berg
2014-10-31 20:33 ` Luis R. Rodriguez
2014-11-03 19:30 ` Luis R. Rodriguez
2014-11-03 19:40 ` Johannes Berg
2014-11-03 19:56 ` Luis R. Rodriguez
2014-11-03 20:20 ` Johannes Berg [this message]
2014-11-03 20:21 ` Luis R. Rodriguez
2014-11-03 20:24 ` Johannes Berg
2014-11-03 20:26 ` Luis R. Rodriguez
2014-10-29 8:21 ` [RFC v2 2/4] backports: replace BACKPORT_PWD with BACKPORT_DIR Luis R. Rodriguez
2014-10-31 7:41 ` Johannes Berg
2014-10-31 19:35 ` Luis R. Rodriguez
2014-10-29 8:21 ` [RFC v2 3/4] backports: use BACKPORT_DIR prefix on kconfig sources Luis R. Rodriguez
2014-10-31 7:46 ` Johannes Berg
2014-10-31 20:03 ` Luis R. Rodriguez
2014-10-29 8:21 ` [RFC v2 4/4] backports: add kernl integration support to gentree.py Luis R. Rodriguez
2014-10-29 15:36 ` Stefan Assmann
2014-10-29 16:00 ` Luis R. Rodriguez
2014-10-31 7:50 ` Johannes Berg
2014-10-31 20:10 ` Luis R. Rodriguez
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=1415046029.2726.6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mmarek@suse.cz \
--cc=sassmann@kpanic.de \
--cc=yann.morin.1998@free.fr \
/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.