Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David J. Fogle <Dave@exitstrategytech.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/rauc: version bump to 1.0
Date: Sat, 12 Jan 2019 17:39:17 +0000	[thread overview]
Message-ID: <2045c659b0da41f8a508dae6666185e1@exitstrategytech.com> (raw)
In-Reply-To: <20190112183941.233b8b85@windsurf.home>

Awesome! Thank you kindly, I will let the RAUC guys know the patch is in. Have a great weekend!



David Fogle

CTO - Exit Strategy


-------- Original message --------
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Date: 1/12/19 11:37 AM (GMT-06:00)
To: "David J. Fogle" <Dave@exitstrategytech.com>
Cc: buildroot at busybox.net
Subject: Re: [Buildroot] [PATCH] package/rauc: version bump to 1.0

Hello,

On Mon, 7 Jan 2019 22:44:07 +0000, David J. Fogle wrote:
> For details see [1]
>
> This bump also deleted the two patch files for the RAUC package. These
> were related to eMMC support being made optional, and workaround for
> olde kernel. Both of these patch sets have been merged into upsteam in
> the rauc git repos.
>
> Older kernel workaound:
> https://github.com/rauc/rauc/commit/993b698c48789baea51f8b7c47b1e057ba328033#diff-b3a0044e6a3b6a8b16933e72f416c8f1
>
> Make eMMC selectable:
> https://github.com/rauc/rauc/commit/f85d1cab07376c7680ef4d9e45a6baf345e24e37#diff-365367c8cde56aafd5cbad767e1c9738
>
> [1] https://github.com/rauc/rauc/releases/tag/v1.0
>
> Signed-off-by: David J Fogle dave at exitstrategytech.com
> ---
>  ...mmc-add-workaround-for-older-kernels.patch |  33 -----
>  ...eMMC-boot-partition-support-optional.patch | 116 ------------------
>  package/rauc/rauc.hash                        |   2 +-
>  package/rauc/rauc.mk                          |   3 +-
>  4 files changed, 2 insertions(+), 152 deletions(-)
>  delete mode 100644 package/rauc/0001-emmc-add-workaround-for-older-kernels.patch
>  delete mode 100644 package/rauc/0002-build-make-eMMC-boot-partition-support-optional.patch

Applied to master after dropping AUTORECONF = YES, as noticed by
Baruch. Thanks!

Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20190112/94039afd/attachment.html>

      reply	other threads:[~2019-01-12 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 22:44 [Buildroot] [PATCH] package/rauc: version bump to 1.0 David J. Fogle
2019-01-08  4:41 ` Baruch Siach
2019-01-09  4:31   ` David J. Fogle
2019-01-09  6:35     ` Baruch Siach
2019-01-10 18:36       ` David J. Fogle
2019-01-12 17:39 ` Thomas Petazzoni
2019-01-12 17:39   ` David J. Fogle [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=2045c659b0da41f8a508dae6666185e1@exitstrategytech.com \
    --to=dave@exitstrategytech.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