public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] hdparm: Update to 9.64
Date: Mon, 01 Aug 2022 15:50:57 +0100	[thread overview]
Message-ID: <43B4B392-61B2-40A3-B15A-C13346F50248@ipfire.org> (raw)
In-Reply-To: <31addfc2-29bc-e31a-c191-84596fd2071f@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>

> On 1 Aug 2022, at 15:27, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Changes according to https://sourceforge.net/p/hdparm/news/2022/07/hdparm-964-is-released/:
> 
> Fixed bug whereby output from "hdparm --Istdin" would sometimes be truncated.
> 
> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
> ---
> lfs/hdparm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/lfs/hdparm b/lfs/hdparm
> index 99196447c..704317a6a 100644
> --- a/lfs/hdparm
> +++ b/lfs/hdparm
> @@ -24,7 +24,7 @@
> 
> include Config
> 
> -VER        = 9.63
> +VER        = 9.64
> 
> THISAPP    = hdparm-$(VER)
> DL_FILE    = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
> 
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
> 
> -$(DL_FILE)_BLAKE2 = 41ee3dda11f17ec9c125b7d680f07ca2d88c3692e2436b8d2550dbd58546b1dde8e61cdf5312c5b09d687dad81826bd848c8eabcb3e01ab09ac6cfb082699238
> +$(DL_FILE)_BLAKE2 = 0196f3ccec4005c542b834d8426cc6f64694783da3d4a064e898e25d17aab3aa0d9621276607169f2104c9a9804f9020554d836ded9efb16367a8ac4c9c9b146
> 
> install : $(TARGET)
> 
> -- 
> 2.35.3


      reply	other threads:[~2022-08-01 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 14:27 Peter Müller
2022-08-01 14:50 ` Michael Tremer [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=43B4B392-61B2-40A3-B15A-C13346F50248@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /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