From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Horatiu Vultur via buildroot <buildroot@buildroot.org>
Cc: Samuel Martin <s.martin49@gmail.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: Re: [Buildroot] [PATCH] package/cfm: new package
Date: Mon, 27 Dec 2021 00:14:36 +0100 [thread overview]
Message-ID: <20211227001436.25792a60@windsurf> (raw)
In-Reply-To: <20211212130745.2240973-1-horatiu.vultur@microchip.com>
On Sun, 12 Dec 2021 14:07:45 +0100
Horatiu Vultur via buildroot <buildroot@buildroot.org> wrote:
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> DEVELOPERS | 1 +
> package/Config.in | 1 +
> package/cfm/Config.in | 17 +++++++++++++
> package/cfm/S65cfm | 55 +++++++++++++++++++++++++++++++++++++++++
> package/cfm/cfm.hash | 3 +++
> package/cfm/cfm.mk | 23 +++++++++++++++++
> package/cfm/cfm.service | 10 ++++++++
> 7 files changed, 110 insertions(+)
> create mode 100644 package/cfm/Config.in
> create mode 100644 package/cfm/S65cfm
> create mode 100644 package/cfm/cfm.hash
> create mode 100644 package/cfm/cfm.mk
> create mode 100644 package/cfm/cfm.service
Applied to master, thanks! The only minor issue (that I have found!)
was the ordering of entries in the DEVELOPERS file: they were not
sorted alphabetically. That's admittedly very minor :)
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-26 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 13:07 [Buildroot] [PATCH] package/cfm: new package Horatiu Vultur via buildroot
2021-12-26 23:14 ` Thomas Petazzoni [this message]
2025-12-16 8:39 ` Thomas Petazzoni via buildroot
2026-01-05 8:23 ` Horatiu Vultur via buildroot
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=20211227001436.25792a60@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=horatiu.vultur@microchip.com \
--cc=s.martin49@gmail.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