From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14221] mv-ddr-marvell fails license validation
Date: Fri, 24 Sep 2021 19:47:00 +0000 [thread overview]
Message-ID: <bug-14221-163-XtyOKzp4RM@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14221-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14221
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Hello,
Thanks for your report. We believe the issue has been fixed with commit
f05136090d (boot/mv-ddr-marvell: fix license file hash).
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-09-24 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 15:22 [Buildroot] [Bug 14221] New: mv-ddr-marvell fails license validation bugzilla
2021-09-23 15:39 ` [Buildroot] [Bug 14221] " bugzilla
2021-09-24 19:47 ` bugzilla [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=bug-14221-163-XtyOKzp4RM@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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