Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [PATCH] eeprog: fix homepage link
@ 2017-12-31 11:25 Baruch Siach
  2017-12-31 11:48 ` Thomas Petazzoni
                   ` (2 more replies)
  0 siblings, 3 replies; 9+ messages in thread
From: Baruch Siach @ 2017-12-31 11:25 UTC (permalink / raw)
  To: buildroot

The current link leads to a 400 Bad Request error page.

Cc: Matt Weber <matthew.weber@rockwellcollins.com>
Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
 package/eeprog/Config.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/package/eeprog/Config.in b/package/eeprog/Config.in
index ff313bdbae96..73582c70f9d4 100644
--- a/package/eeprog/Config.in
+++ b/package/eeprog/Config.in
@@ -3,4 +3,4 @@ config BR2_PACKAGE_EEPROG
 	help
 	  Simple tool to read/write i2c eeprom chips.
 
-	  http://codesink.org/eeprog.html
+	  http://www.codesink.org/eeprog.html
-- 
2.15.1

^ permalink raw reply related	[flat|nested] 9+ messages in thread

* [Buildroot] [PATCH] eeprog: fix homepage link
  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
  2018-01-08 21:48 ` Peter Korsgaard
  2018-01-29 21:36 ` Peter Korsgaard
  2 siblings, 1 reply; 9+ messages in thread
From: Thomas Petazzoni @ 2017-12-31 11:48 UTC (permalink / raw)
  To: buildroot

Hello,

On Sun, 31 Dec 2017 13:25:06 +0200, Baruch Siach wrote:
> The current link leads to a 400 Bad Request error page.
> 
> Cc: Matt Weber <matthew.weber@rockwellcollins.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
>  package/eeprog/Config.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to master, thanks. However, do we still need this package, now
that i2c-tools also builds/installs eeprog ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [PATCH] eeprog: fix homepage link
  2017-12-31 11:48 ` Thomas Petazzoni
@ 2017-12-31 12:26   ` Baruch Siach
  2017-12-31 12:54     ` Thomas Petazzoni
  0 siblings, 1 reply; 9+ messages in thread
From: Baruch Siach @ 2017-12-31 12:26 UTC (permalink / raw)
  To: buildroot

Hi Thomas,

On Sun, Dec 31, 2017 at 12:48:12PM +0100, Thomas Petazzoni wrote:
> On Sun, 31 Dec 2017 13:25:06 +0200, Baruch Siach wrote:
> > The current link leads to a 400 Bad Request error page.
> > 
> > Cc: Matt Weber <matthew.weber@rockwellcollins.com>
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> >  package/eeprog/Config.in | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Applied to master, thanks. However, do we still need this package, now
> that i2c-tools also builds/installs eeprog ?

Probably not. 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?

Are you OK with dropping eeprog? Matt?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [PATCH] eeprog: fix homepage link
  2017-12-31 12:26   ` Baruch Siach
@ 2017-12-31 12:54     ` Thomas Petazzoni
  2017-12-31 13:11       ` Baruch Siach
  0 siblings, 1 reply; 9+ messages in thread
From: Thomas Petazzoni @ 2017-12-31 12:54 UTC (permalink / raw)
  To: buildroot

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

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [PATCH] eeprog: fix homepage link
  2017-12-31 12:54     ` Thomas Petazzoni
@ 2017-12-31 13:11       ` Baruch Siach
  2017-12-31 16:08         ` Thomas Petazzoni
  0 siblings, 1 reply; 9+ messages in thread
From: Baruch Siach @ 2017-12-31 13:11 UTC (permalink / raw)
  To: buildroot

Hi Thomas,

On Sun, Dec 31, 2017 at 01:54:33PM +0100, Thomas Petazzoni wrote:
> 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 ?

They are both based on the same code. It looks like i2c-tools adopted eeprog 
after the last eeprog release in February 2004.

> > 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.

OK. Let's give Matt some time to recover from the holidays and respond before 
I send a patch to remove the eeprog package.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [PATCH] eeprog: fix homepage link
  2017-12-31 13:11       ` Baruch Siach
@ 2017-12-31 16:08         ` Thomas Petazzoni
  2018-01-01 17:32           ` Matthew Weber
  0 siblings, 1 reply; 9+ messages in thread
From: Thomas Petazzoni @ 2017-12-31 16:08 UTC (permalink / raw)
  To: buildroot

Hello,

On Sun, 31 Dec 2017 15:11:08 +0200, Baruch Siach wrote:

> They are both based on the same code. It looks like i2c-tools adopted eeprog 
> after the last eeprog release in February 2004.

OK.

> OK. Let's give Matt some time to recover from the holidays and respond before 
> I send a patch to remove the eeprog package.

Sounds good. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [PATCH] eeprog: fix homepage link
  2017-12-31 16:08         ` Thomas Petazzoni
@ 2018-01-01 17:32           ` Matthew Weber
  0 siblings, 0 replies; 9+ messages in thread
From: Matthew Weber @ 2018-01-01 17:32 UTC (permalink / raw)
  To: buildroot

Baruch, Thomas,

On Sun, Dec 31, 2017 at 10:08 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
>> OK. Let's give Matt some time to recover from the holidays and respond before
>> I send a patch to remove the eeprog package.
>

Removal sounds good to me.

Angelo, thanks for bumping i2c-tools!  Lots of good stuff with this
cleanup and the new tools we now install.

Matt

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [PATCH] eeprog: fix homepage link
  2017-12-31 11:25 [Buildroot] [PATCH] eeprog: fix homepage link Baruch Siach
  2017-12-31 11:48 ` Thomas Petazzoni
@ 2018-01-08 21:48 ` Peter Korsgaard
  2018-01-29 21:36 ` Peter Korsgaard
  2 siblings, 0 replies; 9+ messages in thread
From: Peter Korsgaard @ 2018-01-08 21:48 UTC (permalink / raw)
  To: buildroot

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 > The current link leads to a 400 Bad Request error page.
 > Cc: Matt Weber <matthew.weber@rockwellcollins.com>
 > Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Committed to 2017.11.x, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 9+ messages in thread

* [Buildroot] [PATCH] eeprog: fix homepage link
  2017-12-31 11:25 [Buildroot] [PATCH] eeprog: fix homepage link Baruch Siach
  2017-12-31 11:48 ` Thomas Petazzoni
  2018-01-08 21:48 ` Peter Korsgaard
@ 2018-01-29 21:36 ` Peter Korsgaard
  2 siblings, 0 replies; 9+ messages in thread
From: Peter Korsgaard @ 2018-01-29 21:36 UTC (permalink / raw)
  To: buildroot

>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:

 > The current link leads to a 400 Bad Request error page.
 > Cc: Matt Weber <matthew.weber@rockwellcollins.com>
 > Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Committed to 2017.02.x, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2018-01-29 21:36 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox