All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2] package/c-periphery: Bump version to 2.1.0
Date: Fri, 10 Jan 2020 22:41:01 +0100	[thread overview]
Message-ID: <20200110224101.7dbd25a6@windsurf> (raw)
In-Reply-To: <20200108224034.14703-1-offougajoris@gmail.com>

Hello Joris,

On Wed,  8 Jan 2020 23:40:34 +0100
Joris Offouga <offougajoris@gmail.com> wrote:

> diff --git a/package/c-periphery/Config.in b/package/c-periphery/Config.in
> index 0bfb4b1f11..bcb906da76 100644
> --- a/package/c-periphery/Config.in
> +++ b/package/c-periphery/Config.in
> @@ -1,5 +1,6 @@
>  config BR2_PACKAGE_C_PERIPHERY
>  	bool "c-periphery"
> +	depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_8
>  	help
>  	  c-periphery is a set of C wrapper functions for GPIO, SPI,
>  	  I2C, MMIO, and Serial peripheral I/O interface access in
> @@ -14,3 +15,6 @@ config BR2_PACKAGE_C_PERIPHERY
>  	  integration with other projects, and is MIT licensed.
>  
>  	  https://github.com/vsergeev/c-periphery
> +
> +comment "c-periphery needs kernel headers >= 4.8"

Should have been:

comment "c-periphery needs a toolchain w/ kernel headers >= 4.8"

> +		depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_8

Indentation was not good here, as reported by check-package.

> diff --git a/package/c-periphery/c-periphery.hash b/package/c-periphery/c-periphery.hash
> index 8f3bd8a3da..244f8f60f1 100644
> --- a/package/c-periphery/c-periphery.hash
> +++ b/package/c-periphery/c-periphery.hash
> @@ -1,3 +1,3 @@
>  # Locally calculated
> -sha256 50665a4f298b30e4cc8f7dbd38362fd860cc3746803d00325cb04806674e3166  c-periphery-1.1.3.tar.gz
> -sha256 6b5669a90260126f0600aae98cb10fb5e219269dc9cbd0137f63927b96d5c31d  LICENSE
> +sha256 1c455c42b26818d199ac227cd19714f265623e15d363fdfdf47a2416a4165654  c-periphery-2.1.0.tar.gz
> +sha256 e7b9464cb8511f19ddb40f9cf52fe86b3dfe38b2faed9d7bbc3d5707677ffbe3  LICENSE

Changes in the hash of the license file must be explained in the commit
log.

I have fixed the above issues and applied your patch. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2020-01-10 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 22:40 [Buildroot] [PATCH V2] package/c-periphery: Bump version to 2.1.0 Joris Offouga
2020-01-10 21:41 ` 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=20200110224101.7dbd25a6@windsurf \
    --to=thomas.petazzoni@bootlin.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 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.