All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>,  Joachim Wiberg <troglobit@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 2/2] package/watchdogd: fix sysv init script
Date: Tue, 25 Feb 2025 21:02:46 +0100	[thread overview]
Message-ID: <87ikoxu715.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <87h64mnije.fsf@dell.be.48ers.dk> (Peter Korsgaard's message of "Sat, 22 Feb 2025 15:47:01 +0100")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

>>>>> "Fiona" == Fiona Klute via buildroot <buildroot@buildroot.org> writes:
 >> From: "Fiona Klute (WIWA)" <fiona.klute@gmx.de>
 >> PIDFILE was set incorrectly, watchdogd writes its PID file to
 >> /var/run/watchdogd/pid (note the slash), which is not configurable
 >> without patching.

 >> Restructure the rest of the script to match current style while at it.

 >> Signed-off-by: Fiona Klute (WIWA) <fiona.klute@gmx.de>

 > Committed, thanks.

Committed to 2024.02.x and 2024.11.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-02-25 20:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 13:44 [Buildroot] [PATCH v2 1/2] package/watchdogd: fix use of uninitialized exit status Fiona Klute via buildroot
2025-02-17 13:44 ` [Buildroot] [PATCH v2 2/2] package/watchdogd: fix sysv init script Fiona Klute via buildroot
2025-02-22 14:47   ` Peter Korsgaard
2025-02-25 20:02     ` Peter Korsgaard [this message]
2025-02-22 14:45 ` [Buildroot] [PATCH v2 1/2] package/watchdogd: fix use of uninitialized exit status Peter Korsgaard
2025-02-25 19:57   ` Peter Korsgaard

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=87ikoxu715.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fiona.klute@gmx.de \
    --cc=troglobit@gmail.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 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.