All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ben Shelton <ben.shelton@ni.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/4] busybox: Allow busybox-mdev to RPROVIDES hotplug
Date: Mon, 21 Jul 2014 19:14:26 +0100	[thread overview]
Message-ID: <1405966466.22985.101.camel@ted> (raw)
In-Reply-To: <1405961628-25284-4-git-send-email-ben.shelton@ni.com>

On Mon, 2014-07-21 at 11:53 -0500, Ben Shelton wrote:
> From: Richard Tollerton <rich.tollerton@ni.com>
> 
> This is for symmetry with udev which also RPROVIDES hotplug.
> 
> Signed-off-by: Richard Tollerton <rich.tollerton@ni.com>
> Signed-off-by: Ben Shelton <ben.shelton@ni.com>
> ---
>  meta/recipes-core/busybox/busybox.inc | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
> index bd66e4f..b4b9684 100644
> --- a/meta/recipes-core/busybox/busybox.inc
> +++ b/meta/recipes-core/busybox/busybox.inc
> @@ -42,6 +42,7 @@ SYSTEMD_SERVICE_${PN}-syslog = "busybox-syslog.service"
>  
>  CONFFILES_${PN}-syslog = "${sysconfdir}/syslog-startup.conf.${BPN}"
>  CONFFILES_${PN}-mdev = "${sysconfdir}/mdev.conf"
> +RPROVIDES_${PN}-mdev = "hotplug"
>  
>  RRECOMMENDS_${PN} = "${PN}-syslog ${PN}-udhcpc"

Why add this? I'm curious what would actually use that naming?

The RPROVIDES in udev was for backwards compatibility when hotplug
actually existed iirc, its long since dead?

Cheers,

Richard




  reply	other threads:[~2014-07-21 18:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 16:53 [PATCH 1/4] busybox: mdev: Make /dev/shm world-writable Ben Shelton
2014-07-21 16:53 ` [PATCH 2/4] busybox: mdev: Use mdev.seq Ben Shelton
2014-07-21 16:53 ` [PATCH 3/4] busybox: mdev: Ensure /dev/initctl exists after tmpfs mount Ben Shelton
2014-07-21 16:53 ` [PATCH 4/4] busybox: Allow busybox-mdev to RPROVIDES hotplug Ben Shelton
2014-07-21 18:14   ` Richard Purdie [this message]
2014-07-21 18:44     ` Richard Tollerton

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=1405966466.22985.101.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=ben.shelton@ni.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.