All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kory Maincent via buildroot <buildroot@buildroot.org>
Cc: kory.maincent@bootlin.com, scooby22@web.de
Subject: Re: [Buildroot] [PATCH] package: gcnano-binaries: bump version to 969d115185
Date: Sun, 5 Jun 2022 22:58:19 +0200	[thread overview]
Message-ID: <20220605225819.1f803ff6@windsurf> (raw)
In-Reply-To: <20220531125557.450076-1-kory.maincent@bootlin.com>

On Tue, 31 May 2022 14:55:57 +0200
Kory Maincent via buildroot <buildroot@buildroot.org> wrote:

> From: Kory Maincent <kory.maincent@bootlin.com>
> 
> Update to last version of gcnano-binaries compatible with kernel
> from StMicroelectronics version 5.10
> 
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>

Commit title prefix should always be "package/<pkg>:" and not "package:
<pkg>:".


>  # Locally calculated
> -sha256 afec2ba2f524821452d561b56afd2fc241293ea4a6e8598d1663f58e5d16800f  gcnano-binaries-1534c3eaabb5ae545a8f97e95f853531365a13fc.tar.gz
> +sha256 32d91d6ce6e6551cb7ad0eee4698041fdeb10a4f216e6564adb06408476edc38  gcnano-binaries-969d11518529bb70a132909b02ddcc5736c92d91.tar.gz

The expected separator in the hash file now is two spaces, not one.
This is reported by check-package.

Applied to next with those issues fixed.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-06-05 20:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 12:55 [Buildroot] [PATCH] package: gcnano-binaries: bump version to 969d115185 Kory Maincent via buildroot
2022-06-05 20:58 ` Thomas Petazzoni via buildroot [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=20220605225819.1f803ff6@windsurf \
    --to=buildroot@buildroot.org \
    --cc=kory.maincent@bootlin.com \
    --cc=scooby22@web.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.