Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Nevo Hed <nhed+buildroot@starry.com>,
	 buildroot@buildroot.org,  Paul Cercueil <paul@crapouillou.net>,
	 arnout@rnout.be
Subject: Re: [Buildroot] [PATCH] package/umtprd: expose package build options
Date: Tue, 13 Oct 2026 13:12:50 +0200	[thread overview]
Message-ID: <87ld81ua4t.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <as3sjbzkJ8Teyy8t@windsurf> (Thomas Petazzoni's message of "Tue,  13 Oct 2026 10:34:06 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

Hi,

 >> +config BR2_PACKAGE_UMTPRD_SYSLOG
 >> +	bool "Send output to syslog"

 > Where is the output going otherwise? Shouldn't sending the output to
 > syslog simply be the unconditional default?

 > Peter, Arnout, any opinion on this?

Looking at the code, it indeed seems to be a build time switch:

https://github.com/viveris/uMTP-Responder/blob/b174b03a3c2641a578b9299e540994a35b2f03a9/inc/logs_out.h#L46

Which is not so nice, but oh well.

So I guess it does make sense with the option, unless we say that it
should always log to syslog given that it is a daemon.

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

  reply	other threads:[~2026-10-13 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-04 21:14 [Buildroot] [PATCH] package/umtprd: expose package build options Nevo Hed via buildroot
2026-10-13  8:34 ` Thomas Petazzoni via buildroot
2026-10-13 11:12   ` Peter Korsgaard [this message]
2026-10-13 13:04     ` Thomas Petazzoni via buildroot

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=87ld81ua4t.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=arnout@rnout.be \
    --cc=buildroot@buildroot.org \
    --cc=nhed+buildroot@starry.com \
    --cc=paul@crapouillou.net \
    --cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox