From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/2] package/avrdude: add linux gpio kconfig option
Date: Fri, 19 May 2017 16:39:15 +0200 [thread overview]
Message-ID: <20170519163915.1b083a46@free-electrons.com> (raw)
In-Reply-To: <CANQCQpagwa4KgHS0gw-YL_U2-KUV5_tuFM5a0gqt_1TahN6Vjw@mail.gmail.com>
Hello,
On Fri, 19 May 2017 08:58:25 -0500, Matthew Weber wrote:
> Not sure we reached a conclusion. I guess the question would be,
> right now in buildroot it doesn't enable this option. So if we by
> default go linux-gpio it disables the legacy options which were the
> previous default (kernel's older then sysfs gpio support). I'm good
> either way, but the fundamental package behavior changes.
Package behavior also changes every time we bump a package. So Baruch's
question was whether the size impact was significant or not. If it's
not, then no need to make an option for it.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-19 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 15:08 [Buildroot] [PATCH v2 1/2] package/avrdude: add linux gpio kconfig option Matt Weber
2017-05-18 15:08 ` [Buildroot] [PATCH v2 2/2] package/avrdude: bump to f8893ccf0aceeff67c45f95ae4e86bc7fbe342aa Matt Weber
2017-05-19 13:14 ` [Buildroot] [PATCH v2 1/2] package/avrdude: add linux gpio kconfig option Peter Korsgaard
2017-05-19 13:58 ` Matthew Weber
2017-05-19 14:39 ` Thomas Petazzoni [this message]
2017-05-19 14:48 ` Peter Korsgaard
2017-05-19 15:01 ` Matthew Weber
2017-05-19 15:40 ` Sam Voss
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=20170519163915.1b083a46@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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