From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] bluez: version bump 5.30 -> 5.50
Date: Tue, 9 Oct 2018 17:07:32 +0200 [thread overview]
Message-ID: <20181009150732.kld54dgzzbx45ofg@pengutronix.de> (raw)
In-Reply-To: <20181009131640.nrbsq4eonbdki3sv@pengutronix.de>
On Tue, Oct 09, 2018 at 03:16:40PM +0200, Roland Hieber wrote:
> On Tue, Oct 09, 2018 at 12:52:56PM +0200, Michael Olbrich wrote:
> > On Fri, Oct 05, 2018 at 04:03:06PM +0200, Roland Hieber wrote:
[...]
> > > +config BLUEZ_PROFILE_OBEX
> > > + bool "build with OBEX support"
> > > + help
> > > + Build with support for the OBject EXchange (OBEX) profile.
> > > + Enable this to build obexd.
> > > +
> >
> > Why so many new options? Can we just enable or disable those?
>
> I don't know about other people's use cases, that's why I made them
> optional. But all of them add a fair amount of code to the library.
How much is 'a fair amount' in binary size compared to what's already
there?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-10-09 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 14:03 Roland Hieber
2018-10-08 6:55 ` Juergen Borleis
2018-10-09 10:52 ` Michael Olbrich
2018-10-09 13:16 ` Roland Hieber
2018-10-09 15:07 ` Michael Olbrich [this message]
2018-10-09 13:35 ` Juergen Borleis
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=20181009150732.kld54dgzzbx45ofg@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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