Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/9] package/dhcp: enable selinux module
Date: Sat, 4 Nov 2023 16:11:47 +0100	[thread overview]
Message-ID: <20231104161147.2f73b5c7@windsurf> (raw)
In-Reply-To: <20231010170133.2981698-1-adam.duskett@amarulasolutions.com>

On Tue, 10 Oct 2023 19:01:25 +0200
Adam Duskett <adam.duskett@amarulasolutions.com> wrote:

> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
> ---
>  package/dhcp/dhcp.mk | 1 +
>  1 file changed, 1 insertion(+)

Series applied to master, thanks.

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

      parent reply	other threads:[~2023-11-04 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 17:01 [Buildroot] [PATCH 1/9] package/dhcp: enable selinux module Adam Duskett
2023-10-10 17:01 ` [Buildroot] [PATCH 2/9] package/docker: " Adam Duskett
2023-10-10 17:01 ` [Buildroot] [PATCH 3/9] package/mono: " Adam Duskett
2023-10-10 17:01 ` [Buildroot] [PATCH 4/9] package/qemu: " Adam Duskett
2023-10-10 17:01 ` [Buildroot] [PATCH 5/9] package/tzdata: " Adam Duskett
2023-10-10 17:01 ` [Buildroot] [PATCH 6/9] package/watchdog: " Adam Duskett
2023-10-10 17:01 ` [Buildroot] [PATCH 7/9] package/xen: " Adam Duskett
2023-10-10 17:01 ` [Buildroot] [PATCH 8/9] package/zabbix: " Adam Duskett
2023-10-10 17:01 ` [Buildroot] [PATCH 9/9] package/zfs: " Adam Duskett
2023-11-04 15:11 ` 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=20231104161147.2f73b5c7@windsurf \
    --to=buildroot@buildroot.org \
    --cc=adam.duskett@amarulasolutions.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