Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] lshw version bump
@ 2016-07-29  9:27 Sokolowski, Hubert
  2016-07-29 13:44 ` Thomas Petazzoni
  0 siblings, 1 reply; 2+ messages in thread
From: Sokolowski, Hubert @ 2016-07-29  9:27 UTC (permalink / raw)
  To: buildroot

Dear All,

We were wondering if you are planning to bump a version of lshw?
We discovered that version B.02.17 (which was released in 2013) 
 can cause segmentation fault and crash on recent hardware.
Version B.02.18 was released this year and contains several bug fixes.
Please apply the patch that is attached if it is acceptable for you.

-- 
Best Regards,
Hubert Sokolowski
Intel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-lshw-bump-version-to-B.02.18.patch
Type: application/octet-stream
Size: 3529 bytes
Desc: 0001-lshw-bump-version-to-B.02.18.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160729/ad390e07/attachment.obj>

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

* [Buildroot] lshw version bump
  2016-07-29  9:27 [Buildroot] lshw version bump Sokolowski, Hubert
@ 2016-07-29 13:44 ` Thomas Petazzoni
  0 siblings, 0 replies; 2+ messages in thread
From: Thomas Petazzoni @ 2016-07-29 13:44 UTC (permalink / raw)
  To: buildroot

Hello,

On Fri, 29 Jul 2016 09:27:02 +0000, Sokolowski, Hubert wrote:

> We were wondering if you are planning to bump a version of lshw?

We do version bumps when we receive patches that do so :-)

> We discovered that version B.02.17 (which was released in 2013) 
>  can cause segmentation fault and crash on recent hardware.
> Version B.02.18 was released this year and contains several bug fixes.
> Please apply the patch that is attached if it is acceptable for you.

Your patch looks good. Could you send it inline and no as an
attachment, by using "git send-email" ?

Another question, could you give a few more details about why you
remove all the patches? You simply indicate in the commit log that they
are "obsolete", but that's a bit short. Are they obsolete because they
have been merged upstream? Are they obsolete because the problem no
longer occurs due to other changes upstream?

Thanks a lot!

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

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

end of thread, other threads:[~2016-07-29 13:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-07-29  9:27 [Buildroot] lshw version bump Sokolowski, Hubert
2016-07-29 13:44 ` Thomas Petazzoni

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