All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Stephan Henningsen <stephan@asklandd.dk>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] linux-firmware-bump-to-20221109.patch
Date: Sun, 11 Dec 2022 11:31:10 +0100	[thread overview]
Message-ID: <20221211113110.34f98ea3@windsurf> (raw)
In-Reply-To: <D5CLMR.W52FYUR7ME313@asklandd.dk>

Hello Stephan,

On Thu, 08 Dec 2022 22:10:25 +0100
Stephan Henningsen <stephan@asklandd.dk> wrote:

> linux-firmware.mk: bump to release 20221109
> linux-firmware.hash: add hash of bumped tarball, remove hash of deleted 
> files
> 
> Signed-off-by: Stephan Henningsen <stephan+buildroot@asklandd.dk>

I'm afraid that as others have pointed out, your patch arrived badly
damaged on the mailing list. Please use git send-email, or teach your
e-mail client to not line-wrap the contents of the e-mails you're
sending when they contain a patch.

Nevertheless, I took your patch "manually" and applied it. However, I
reverted the parts where you removed the hash of some files: they still
exist in the newer version of linux-firmware. In addition, your hash
for the WHENCE file was wrong.

I fixed that up and made the following commit:

  https://gitlab.com/buildroot.org/buildroot/-/commit/bec9e5f7852f6fefb234877dff45916d921c4b18

Best regards,

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-12-11 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 21:10 [Buildroot] linux-firmware-bump-to-20221109.patch Stephan Henningsen
2022-12-11 10:31 ` 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=20221211113110.34f98ea3@windsurf \
    --to=buildroot@buildroot.org \
    --cc=stephan@asklandd.dk \
    --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.