Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@linux-m68k.org>
To: Colin Ian King <colin.i.king@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][next] m68k: remove trailing space after \n newline
Date: Mon, 2 Sep 2024 12:10:35 +1000	[thread overview]
Message-ID: <9bc18998-821b-42d1-8c6b-abc528be33f2@linux-m68k.org> (raw)
In-Reply-To: <20240901155846.142816-1-colin.i.king@gmail.com>

Hi Colin,

On 2/9/24 01:58, Colin Ian King wrote:
> There is a extraneous space after a newline in a pr_debug message.
> Remove it.
> 
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>

Thanks, looks good.
I have applied to for-next branch of m68knommu git tree.

Regards
Greg


> ---
>   arch/m68k/kernel/setup_no.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/m68k/kernel/setup_no.c b/arch/m68k/kernel/setup_no.c
> index 37fb663559b4..c926da9d5ec2 100644
> --- a/arch/m68k/kernel/setup_no.c
> +++ b/arch/m68k/kernel/setup_no.c
> @@ -138,7 +138,7 @@ void __init setup_arch(char **cmdline_p)
>   
>   	pr_debug("KERNEL -> TEXT=0x%p-0x%p DATA=0x%p-0x%p BSS=0x%p-0x%p\n",
>   		 _stext, _etext, _sdata, _edata, __bss_start, __bss_stop);
> -	pr_debug("MEMORY -> ROMFS=0x%p-0x%06lx MEM=0x%06lx-0x%06lx\n ",
> +	pr_debug("MEMORY -> ROMFS=0x%p-0x%06lx MEM=0x%06lx-0x%06lx\n",
>   		 __bss_stop, memory_start, memory_start, memory_end);
>   
>   	memblock_add(_rambase, memory_end - _rambase);

      reply	other threads:[~2024-09-02  2:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01 15:58 [PATCH][next] m68k: remove trailing space after \n newline Colin Ian King
2024-09-02  2:10 ` Greg Ungerer [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=9bc18998-821b-42d1-8c6b-abc528be33f2@linux-m68k.org \
    --to=gerg@linux-m68k.org \
    --cc=colin.i.king@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox