From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Brandon Maier via buildroot <buildroot@buildroot.org>
Cc: Brandon Maier <brandon.maier@collins.com>
Subject: Re: [Buildroot] [PATCH 0/3] package/atftp: add init script and support/testing
Date: Tue, 9 Jul 2024 22:25:14 +0200 [thread overview]
Message-ID: <20240709222514.0c8af184@windsurf> (raw)
In-Reply-To: <20240702-atftp-sysvinit-v1-0-f26694337129@collins.com>
On Tue, 02 Jul 2024 15:18:43 +0000
Brandon Maier via buildroot <buildroot@buildroot.org> wrote:
> Brandon Maier (3):
> package/atftp: add sysvinit script
> support/testing: add atftp test
> DEVELOPERS: add myself for package/atftp
Thanks, series applied. On PATCH 1/3, I did some small tweaks to make
your init script look more like our canonical example in the Buildroot
manual. Also on PATCH 2/3, I added an entry in the DEVELOPERS to have
you as the maintainer of the atftp test.
Thanks!
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
prev parent reply other threads:[~2024-07-09 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 15:18 [Buildroot] [PATCH 0/3] package/atftp: add init script and support/testing Brandon Maier via buildroot
2024-07-02 15:18 ` [Buildroot] [PATCH 1/3] package/atftp: add sysvinit script Brandon Maier via buildroot
2024-07-02 15:18 ` [Buildroot] [PATCH 2/3] support/testing: add atftp test Brandon Maier via buildroot
2024-07-02 15:18 ` [Buildroot] [PATCH 3/3] DEVELOPERS: add myself for package/atftp Brandon Maier via buildroot
2024-07-09 20:25 ` 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=20240709222514.0c8af184@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.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