From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] eeprog: fix homepage link
Date: Sun, 31 Dec 2017 13:54:33 +0100 [thread overview]
Message-ID: <20171231135433.1d0b98a9@windsurf> (raw)
In-Reply-To: <20171231122618.ezq72ybk2rem2wvv@sapphire.tkos.co.il>
Hello,
On Sun, 31 Dec 2017 14:26:18 +0200, Baruch Siach wrote:
> > Applied to master, thanks. However, do we still need this package, now
> > that i2c-tools also builds/installs eeprog ?
>
> Probably not.
Do they provide the same features ?
> Event worse. When both i2c-tools and eeprog are enabled, the
> target /usr/bin/eeprog depends on the build order. Has the autobuilder caught
> this file overwrite?
It will, be currently such errors are not errors, but warnings: they
don't make the build fail. Yann recently posted a patch that would
allow to turn such warnings into errors, but there are so many of such
overwrites today that enabling such an option in the autobuilders would
turn almost all results to NOK.
> Are you OK with dropping eeprog? Matt?
I don't use eeprog, so I don't really care. But if the standalone
eeprog and the one on i2c-tools are equivalent, I think it makes sense
to keep the one from i2c-tools.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-31 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 11:25 [Buildroot] [PATCH] eeprog: fix homepage link Baruch Siach
2017-12-31 11:48 ` Thomas Petazzoni
2017-12-31 12:26 ` Baruch Siach
2017-12-31 12:54 ` Thomas Petazzoni [this message]
2017-12-31 13:11 ` Baruch Siach
2017-12-31 16:08 ` Thomas Petazzoni
2018-01-01 17:32 ` Matthew Weber
2018-01-08 21:48 ` Peter Korsgaard
2018-01-29 21:36 ` Peter Korsgaard
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=20171231135433.1d0b98a9@windsurf \
--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