[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150704092000.322dc4e6@grimm.local.home>
Date: Sat, 4 Jul 2015 09:20:00 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
David Cohen <david.a.cohen@...ux.intel.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Alan Cox <alan@...ux.intel.com>,
"Stuart R. Anderson" <stuart.r.anderson@...el.com>
Subject: Re: [RFC][PATCH] x86: Allow early_printk to use console style param
like 115200n8
On Sat, 4 Jul 2015 13:03:59 +0200
Ingo Molnar <mingo@...nel.org> wrote:
> > + /*
> > + * In case the input is like console with text after the baud
> > + * rate. e.g. 115200n8. kstrtoul() will error on such input.
> > + */
> > + for (p = s; *p && isdigit(*p); p++)
> > + ;
> > + *p = 0;
> > +
> > if (kstrtoul(s, 0, &baud) < 0 || baud == 0)
> > baud = DEFAULT_BAUD;
>
>
This was actually one of those cases where I wanted to show that
keeping the old function around is better than the alternative ;-)
If people say we need to phase out simple_strtoull(), then I wanted to
show what kinds of hacks we will have if that happens.
I was hoping that someone would point out that simple_strtoull() is a
better solution. :)
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists