All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-clk@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1] HACK: earlyprintk: Allow nocfg and keep together
Date: Fri, 19 Jan 2018 19:35:17 +0200	[thread overview]
Message-ID: <20180119173517.22474-1-andriy.shevchenko@linux.intel.com> (raw)

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
 arch/x86/kernel/early_printk.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kernel/early_printk.c b/arch/x86/kernel/early_printk.c
index 7e07427df3f4..9606e45da124 100644
--- a/arch/x86/kernel/early_printk.c
+++ b/arch/x86/kernel/early_printk.c
@@ -204,7 +204,7 @@ static __init void early_serial_init(char *s)
 	 * Lastly, initialize the hardware
 	 */
 	if (*s) {
-		if (strcmp(s, "nocfg") == 0)
+		if (strncmp(s, "nocfg", 5) == 0)
 			/* Sometimes, we want to leave the UART alone
 			 * and assume the BIOS has set it up correctly.
 			 * "nocfg" tells us this is the case, and we
@@ -320,7 +320,7 @@ static __init void early_pci_serial_init(char *s)
 	 * Lastly, initialize the hardware
 	 */
 	if (*s) {
-		if (strcmp(s, "nocfg") == 0)
+		if (strncmp(s, "nocfg", 5) == 0)
 			/* Sometimes, we want to leave the UART alone
 			 * and assume the BIOS has set it up correctly.
 			 * "nocfg" tells us this is the case, and we
-- 
2.15.1

             reply	other threads:[~2018-01-19 17:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19 17:35 Andy Shevchenko [this message]
2018-01-19 17:43 ` [PATCH v1] HACK: earlyprintk: Allow nocfg and keep together Andy Shevchenko

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=20180119173517.22474-1-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.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.