All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: Norbert Lange <nolange79@gmail.com>,
	Sen Hastings <sen@phobosdpl.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/systemd: fix typos in comments
Date: Thu, 3 Aug 2023 21:12:09 +0200	[thread overview]
Message-ID: <20230803191208.GM421096@scaer> (raw)
In-Reply-To: <20230803073704.1379495-1-luca.ceresoli@bootlin.com>

Luca, All,

On 2023-08-03 09:37 +0200, Luca Ceresoli via buildroot spake thusly:
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

Both applied to master, thanks!

Regards,
Yann E. MORIN.

> ---
>  package/systemd/systemd.mk | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/package/systemd/systemd.mk b/package/systemd/systemd.mk
> index 0aa1da3fb80c..86b1715076a9 100644
> --- a/package/systemd/systemd.mk
> +++ b/package/systemd/systemd.mk
> @@ -661,9 +661,9 @@ SYSTEMD_TARGET_FINALIZE_HOOKS += \
>  	SYSTEMD_INSTALL_RESOLVCONF_HOOK
>  
>  ifneq ($(call qstrip,$(BR2_TARGET_GENERIC_GETTY_PORT)),)
> -# systemd provides multiple units to autospawn getty as neede
> +# systemd provides multiple units to autospawn getty as needed
>  # * getty@.service to start a getty on normal TTY
> -# * sertial-getty@.service to start a getty on serial lines
> +# * serial-getty@.service to start a getty on serial lines
>  # * console-getty.service for generic /dev/console
>  # * container-getty@.service for a getty on /dev/pts/*
>  #
> @@ -671,7 +671,7 @@ ifneq ($(call qstrip,$(BR2_TARGET_GENERIC_GETTY_PORT)),)
>  # * read the console= kernel command line parameter
>  # * enable one of the above units depending on what it finds
>  #
> -# Systemd defaults to enablinb getty@tty1.service
> +# Systemd defaults to enabling getty@tty1.service
>  #
>  # What we want to do
>  # * Enable a getty on $BR2_TARGET_GENERIC_TTY_PATH
> -- 
> 2.34.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2023-08-03 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-03  7:37 [Buildroot] [PATCH 1/2] package/systemd: fix typos in comments Luca Ceresoli via buildroot
2023-08-03  7:37 ` [Buildroot] [PATCH 2/2] package/systemd: fix wrong variable name in comment Luca Ceresoli via buildroot
2023-08-31 11:10   ` Peter Korsgaard
2023-08-03 19:12 ` Yann E. MORIN [this message]
2023-08-31 11:10 ` [Buildroot] [PATCH 1/2] package/systemd: fix typos in comments 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=20230803191208.GM421096@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=nolange79@gmail.com \
    --cc=sen@phobosdpl.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.