Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] lshw version bump
Date: Fri, 29 Jul 2016 15:44:53 +0200	[thread overview]
Message-ID: <20160729154453.75c1c684@free-electrons.com> (raw)
In-Reply-To: <C039B2B452EFF24BA495644ED973419137DA1A4C@IRSMSX107.ger.corp.intel.com>

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

      reply	other threads:[~2016-07-29 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  9:27 [Buildroot] lshw version bump Sokolowski, Hubert
2016-07-29 13:44 ` Thomas Petazzoni [this message]

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=20160729154453.75c1c684@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