From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP1/2: fix SoC name printing
Date: Thu, 29 Nov 2018 12:06:58 -0800 [thread overview]
Message-ID: <20181129200657.GE53235@atomide.com> (raw)
In-Reply-To: <20181119194641.303-1-aaro.koskinen@iki.fi>
* Aaro Koskinen <aaro.koskinen@iki.fi> [181119 11:46]:
> Currently we get extra newlines on OMAP1/2 when the SoC name is printed:
>
> [ 0.000000] OMAP1510
> [ 0.000000] revision 2 handled as 15xx id: bc058c9b93111a16
>
> [ 0.000000] OMAP2420
> [ 0.000000]
>
> Fix by using pr_cont.
Applying into omap-for-v4.21/omap1 thanks.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP1/2: fix SoC name printing
Date: Thu, 29 Nov 2018 12:06:58 -0800 [thread overview]
Message-ID: <20181129200657.GE53235@atomide.com> (raw)
In-Reply-To: <20181119194641.303-1-aaro.koskinen@iki.fi>
* Aaro Koskinen <aaro.koskinen@iki.fi> [181119 11:46]:
> Currently we get extra newlines on OMAP1/2 when the SoC name is printed:
>
> [ 0.000000] OMAP1510
> [ 0.000000] revision 2 handled as 15xx id: bc058c9b93111a16
>
> [ 0.000000] OMAP2420
> [ 0.000000]
>
> Fix by using pr_cont.
Applying into omap-for-v4.21/omap1 thanks.
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-11-29 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 19:46 [PATCH] ARM: OMAP1/2: fix SoC name printing Aaro Koskinen
2018-11-19 19:46 ` Aaro Koskinen
2018-11-29 20:06 ` Tony Lindgren [this message]
2018-11-29 20:06 ` Tony Lindgren
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=20181129200657.GE53235@atomide.com \
--to=tony@atomide.com \
--cc=aaro.koskinen@iki.fi \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.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 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.