Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/2] package/linuxptp: rename systemd service scripts
Date: Sat, 14 Mar 2020 15:38:25 +0100	[thread overview]
Message-ID: <20200314153825.6b2e8a26@windsurf> (raw)
In-Reply-To: <20200312190434.973-3-heiko.thiery@gmail.com>

On Thu, 12 Mar 2020 20:04:36 +0100
Heiko Thiery <heiko.thiery@gmail.com> wrote:

> Use the same name as for the SysVinit scripts. This name is also used in
> debian.
> 
> linuxptp-system-clock.service -> phc2sys.service
> linuxptp.service -> ptp4l.service
> 
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> Tested-by: Carlos Santos <unixmania@gmail.com>
> ---
>  package/linuxptp/linuxptp.mk                              | 8 ++++----
>  .../{linuxptp-system-clock.service => phc2sys.service}    | 2 +-
>  package/linuxptp/{linuxptp.service => ptp4l.service}      | 2 +-
>  3 files changed, 6 insertions(+), 6 deletions(-)
>  rename package/linuxptp/{linuxptp-system-clock.service => phc2sys.service} (89%)
>  rename package/linuxptp/{linuxptp.service => ptp4l.service} (87%)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2020-03-14 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 19:04 [Buildroot] [PATCH v4 0/1] package/linuxptp: make initscript options configurable Heiko Thiery
2020-03-12 19:04 ` [Buildroot] [PATCH v4 1/2] " Heiko Thiery
2020-03-12 20:39   ` Carlos Santos
2020-03-12 21:09     ` Heiko Thiery
2020-03-14 14:38   ` Thomas Petazzoni
2020-03-12 19:04 ` [Buildroot] [PATCH v4 2/2] package/linuxptp: rename systemd service scripts Heiko Thiery
2020-03-12 20:40   ` Carlos Santos
2020-03-14 14:38   ` Thomas Petazzoni [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=20200314153825.6b2e8a26@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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