From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Rustad <mark.d.rustad@intel.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH v8 0/3] x86/earlyprintk: setup serial earlyprintk as early as possible
Date: Tue, 26 May 2015 17:58:54 +0300 [thread overview]
Message-ID: <1432652334.8736.39.camel@linux.intel.com> (raw)
In-Reply-To: <CANCZXo6MnhoGQv3pCFCjG+ffimJ7Jir_SvCd0CZa8k2-tBm-qg@mail.gmail.com>
On Tue, 2015-05-26 at 20:11 +0600, Alexander Kuleshov wrote:
> 2015-05-26 19:57 GMT+06:00 Borislav Petkov <bp@suse.de>:
> > On Tue, May 26, 2015 at 07:20:02PM +0600, Alexander Kuleshov wrote:
> >> To be able to use early_printk and serial console between kernel
> >> decompression and parse_eary_param.
> >
> > So no real use case - only a "just because we can" case.
> >
>
> It is not "just because we can". There is some code after kernel decompression
> and before parse_early_param and earlyprintk can be useful for
> printing debugging information
> in this case.
So, what is *yours* use case? From here you describe a *potential* use
case, not a real one.
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2015-05-26 14:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 13:06 [PATCH v8 0/3] x86/earlyprintk: setup serial earlyprintk as early as possible Alexander Kuleshov
2015-05-26 13:07 ` [PATCH v8 1/3] x86/setup: introduce setup_bultin_cmdline Alexander Kuleshov
2015-05-26 13:07 ` [PATCH v8 2/3] x86/setup: handle builtin command line as early as possible Alexander Kuleshov
2015-05-26 13:08 ` [PATCH v8 3/3] x86/earlyprintk: setup earlyprintk " Alexander Kuleshov
2015-05-26 13:17 ` [PATCH v8 0/3] x86/earlyprintk: setup serial " Borislav Petkov
2015-05-26 13:20 ` Alexander Kuleshov
2015-05-26 13:57 ` Borislav Petkov
2015-05-26 14:11 ` Alexander Kuleshov
2015-05-26 14:58 ` Andy Shevchenko [this message]
2015-05-26 21:34 ` Borislav Petkov
2015-05-27 7:33 ` Alexander Kuleshov
2015-05-27 12:01 ` Borislav Petkov
2015-05-27 12:12 ` Alexander Kuleshov
2015-05-27 12:51 ` Borislav Petkov
2015-05-28 8:01 ` Alexander Kuleshov
2015-05-29 16:55 ` Borislav Petkov
2015-06-02 11:25 ` Alexander Kuleshov
-- strict thread matches above, loose matches on Subject: below --
2015-05-18 9:19 [PATCH v7 " Alexander Kuleshov
2015-05-26 13:04 ` [PATCH v8 " Alexander Kuleshov
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=1432652334.8736.39.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bp@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kuleshovmail@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.d.rustad@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=yinghai@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.