From: Yunus Bas via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Luc Beaufils <luc.beaufils@savoirfairelinux.com>
Cc: buildroot <buildroot@buildroot.org>,
Thomas Perrot <thomas.perrot@bootlin.com>
Subject: Re: [Buildroot] [PATCH v2 0/2] Support for i.MX Code Signing Tools
Date: Thu, 14 Aug 2025 11:04:36 +0000 [thread overview]
Message-ID: <0ad60b664df5cab40ff708e78ea025ec79c2926c.camel@phytec.de> (raw)
In-Reply-To: <20250814095413.45e41061@windsurf>
[-- Attachment #1.1: Type: text/plain, Size: 2025 bytes --]
Hi Thomas, Luc,
thank you for the fast reply. Currently, I'm using the series in a customer project, so there is no problem with the source. The point is, this patch is still not upstream. I have a few follow-up patches which I would like to send upstream but are pending because they depend on this series. Will this series be approved and applied?
Best regards,
Yunus
Am Donnerstag, dem 14.08.2025 um 09:54 +0200 schrieb Thomas Petazzoni:
On Thu, 14 Aug 2025 03:41:41 -0400 (EDT)
Luc Beaufils <luc.beaufils@savoirfairelinux.com<mailto:luc.beaufils@savoirfairelinux.com>> wrote:
The 3.4.0+dfsg version has been removed from the debian repository.
The series should bump to the 3.4.1+dfsg version.
The series is correctly using https://snapshot.debian.org/archive/,
where the tarballs never disappear and have a stable URL. That of
course doesn't mean a version bump would not be useful, but the current
series is correctly using tarballs that still exist.
Best regards,
Thomas
--
Yunus Bas
-Software Entwicklung-
PHYTEC Messtechnik GmbH
Barcelona-Allee 1
55129 Mainz
Germany
Tel.: +49 (0)6131 9221-466
Web: www.phytec.de<http://www.phytec.de/>
Sie finden uns auch auf: Facebook<https://www.facebook.com/PHYTEC.Mainz>, LinkedIn,<http://www.linkedin.com/company/phytec-messtechnik-gmbh> Xing<https://www.xing.com/companies/phytecmesstechnikgmbh>, YouTube<http://www.youtube.com/user/PhytecMainz>
PHYTEC Messtechnik GmbH | Barcelona-Allee 1 | 55129 Mainz, Germany
Geschäftsführer: Dipl.-Ing. Michael Mitezki, Dipl.-Ing. Bodo Huber, Dipl.-Ing. (FH) Marcus Lickes | Handelsregister Mainz HRB 4656 | Finanzamt Mainz | St.Nr.: 26/665/00608, USt-ID: DE 149059855
This E-Mail may contain confidential or privileged information. If you are not the intended recipient (or have received this E-Mail in error) please notify the sender immediately and destroy this E-Mail. Any unauthorized copying, disclosure or distribution of the material in this E-Mail is strictly forbidden.
[-- Attachment #1.2: Type: text/html, Size: 14299 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-14 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <657a4a78e8df2a586faebb61d46ff3e8cfc7032d.camel@phytec.de>
2025-08-14 7:41 ` [Buildroot] [PATCH v2 0/2] Support for i.MX Code Signing Tools Luc Beaufils
2025-08-14 7:54 ` Thomas Petazzoni via buildroot
2025-08-14 11:04 ` Yunus Bas via buildroot [this message]
2025-03-07 9:59 Luc BEAUFILS
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=0ad60b664df5cab40ff708e78ea025ec79c2926c.camel@phytec.de \
--to=buildroot@buildroot.org \
--cc=Y.Bas@phytec.de \
--cc=luc.beaufils@savoirfairelinux.com \
--cc=thomas.perrot@bootlin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox