Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "An?bal Lim?n" <limon.anibal@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	otavio.salvador@ossystems.com.br,
	richard.purdie@linuxfoundation.org
Subject: Re: [OE-core] [PATCHv2]] recipes-support: rng-tools change systemd service name
Date: Wed, 27 Jul 2022 12:44:06 +0200	[thread overview]
Message-ID: <20220727124406.4f7bc8ec@booty> (raw)
In-Reply-To: <20220726193322.1569574-1-limon.anibal@gmail.com>

Hello Aníbal,

On Tue, 26 Jul 2022 14:33:22 -0500
"An?bal Lim?n" <limon.anibal@gmail.com> wrote:

> From: Aníbal Limón <limon.anibal@gmail.com>
> 
> Change systemd service name from rngd -> rng-tools to avoid load twice
> the service when sysvinit compatibility is enabled,
> 
> ...
> root@:~# ps  | grep rng
>    23 root         0 SW   [hwrng]
> 13109 root      3528 R    /usr/sbin/rngd -f -r /dev/hwrng
> 13117 root      2348 S    grep rng
> 29418 root     12756 S    /usr/sbin/rngd -r /dev/hwrng
> ...
> 
> Signed-off-by: Aníbal Limón <limon.anibal@gmail.com>
> ---
>  .../rng-tools/{rngd.service => rng-tools.service}    |  0
>  meta/recipes-support/rng-tools/rng-tools_6.15.bb     | 12 ++++++------
>  2 files changed, 6 insertions(+), 6 deletions(-)
>  rename meta/recipes-support/rng-tools/rng-tools/{rngd.service => rng-tools.service} (100%)
> 
> diff --git a/meta/recipes-support/rng-tools/rng-tools/rngd.service b/meta/recipes-support/rng-tools/rng-tools/rng-tools.service
> similarity index 100%
> rename from meta/recipes-support/rng-tools/rng-tools/rngd.service
> rename to meta/recipes-support/rng-tools/rng-tools/rng-tools.service
> diff --git a/meta/recipes-support/rng-tools/rng-tools_6.15.bb b/meta/recipes-support/rng-tools/rng-tools_6.15.bb
> index 0696351903..efc08b5e0a 100644
> --- a/meta/recipes-support/rng-tools/rng-tools_6.15.bb
> +++ b/meta/recipes-support/rng-tools/rng-tools_6.15.bb
> @@ -11,7 +11,7 @@ DEPENDS = "sysfsutils openssl"
>  SRC_URI = "git://github.com/nhorman/rng-tools.git;branch=master;protocol=https \
>             file://init \
>             file://default \
> -           file://rngd.service \
> +           file://rng-tools.service \

This feels strange to me: "rng-tools" does not look like a daemon name,
but rather a, well, tools name. Maybe "rng-daemon" would clarify?

Still I'm taking this patch for testing, I'll replace it with v2 should
you send one.

However please note there is an extra ']' in the subject: [PATCHv2]]
should be [PATCHv2]. This leads 'git am' to produce a commit starting
with a "] " prefix. I fixed it while applying, however you should check
that in the future.

Best regards.
-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2022-07-27 10:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 19:33 [PATCHv2]] recipes-support: rng-tools change systemd service name An?bal Lim?n
2022-07-27 10:44 ` Luca Ceresoli [this message]
2022-07-27 14:51   ` [OE-core] " Anibal Limón
2022-07-28  4:03     ` Khem Raj
2022-07-28 13:34       ` Anibal Limón
2022-07-28 13:48         ` Richard Purdie

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=20220727124406.4f7bc8ec@booty \
    --to=luca.ceresoli@bootlin.com \
    --cc=limon.anibal@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=richard.purdie@linuxfoundation.org \
    /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