mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bastian Krause <bst@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] procps: add pidwait
Date: Tue, 24 Sep 2024 17:07:53 +0200	[thread overview]
Message-ID: <20240924150753.2500060-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240918133214.599106-1-bst@pengutronix.de>

Thanks, applied as 08b96ff5b6111b95f47062aa90042a6447f0fe25.

Michael

[sent from post-receive hook]

On Tue, 24 Sep 2024 17:07:53 +0200, Bastian Krause <bst@pengutronix.de> wrote:
> Signed-off-by: Bastian Krause <bst@pengutronix.de>
> Message-Id: <20240918133214.599106-1-bst@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/procps.in b/rules/procps.in
> index 1084ede59e2a..1d8c9e35c413 100644
> --- a/rules/procps.in
> +++ b/rules/procps.in
> @@ -48,6 +48,12 @@ config PROCPS_PGREP
>  comment "busybox' pgrep is selected!"
>  	depends on BUSYBOX_PGREP
>  
> +config PROCPS_PIDWAIT
> +	bool
> +	prompt "pidwait"
> +	help
> +	  The pidwait program can wait for running processes.
> +
>  config PROCPS_PIDOF
>  	bool
>  	prompt "pidof"
> diff --git a/rules/procps.make b/rules/procps.make
> index 40110d909862..44153fe060dc 100644
> --- a/rules/procps.make
> +++ b/rules/procps.make
> @@ -89,6 +89,9 @@ endif
>  ifdef PTXCONF_PROCPS_PIDOF
>  	@$(call install_copy, procps, 0, 0, 0755, -, /usr/bin/pidof)
>  endif
> +ifdef PTXCONF_PROCPS_PIDWAIT
> +	@$(call install_copy, procps, 0, 0, 0755, -, /usr/bin/pidwait)
> +endif
>  ifdef PTXCONF_PROCPS_PKILL
>  	@$(call install_copy, procps, 0, 0, 0755, -, /usr/bin/pkill)
>  endif



      reply	other threads:[~2024-09-24 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 13:32 [ptxdist] [PATCH] " Bastian Krause
2024-09-24 15:07 ` Michael Olbrich [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=20240924150753.2500060-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=bst@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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