mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [RFC PATCH 0/3] util-linux-ng improvements
Date: Thu, 22 Mar 2018 09:18:35 +0100	[thread overview]
Message-ID: <20180322081838.350-1-ada@thorsis.com> (raw)

Hei hei,

the recently published util-linux 2.32 supports an improved version of
lscpu on ARM CPUs [1], which I was interested in. After adding an
option to install lscpu to the target (first patch), I found I could
not easily test rc tarballs (second patch). The third patch is the
version bump, but I'm not sure about all things configure_helper.py
complained about. So I marked the whole patch series as RFC.

Greets
Alex

[1] https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/v2.32/v2.32-ReleaseNotes

Alexander Dahl (3):
  util-linux-ng: Add lscpu to installable tools
  util-linux-ng: Change regex to allow rc tarballs
  util-linux-ng: Upgrade from v2.31.1 to v2.32

 rules/util-linux-ng.in   |  7 +++++++
 rules/util-linux-ng.make | 10 +++++++---
 2 files changed, 14 insertions(+), 3 deletions(-)

-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2018-03-22  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22  8:18 Alexander Dahl [this message]
2018-03-22  8:18 ` [ptxdist] [RFC PATCH 1/3] util-linux-ng: Add lscpu to installable tools Alexander Dahl
2018-03-22  8:18 ` [ptxdist] [RFC PATCH 2/3] util-linux-ng: Change regex to allow rc tarballs Alexander Dahl
2018-03-22  8:18 ` [ptxdist] [RFC PATCH 3/3] util-linux-ng: Upgrade from v2.31.1 to v2.32 Alexander Dahl
2018-03-23  9:02   ` Alexander Dahl
2018-03-26  6:36     ` Michael Olbrich

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=20180322081838.350-1-ada@thorsis.com \
    --to=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    /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