From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Kevin Hilman <khilman@baylibre.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Petr Mladek <pmladek@suse.com>, Mark Brown <broonie@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: kernel CI: printk loglevels in kernel boot logs?
Date: Fri, 1 Dec 2017 10:25:40 +0900 [thread overview]
Message-ID: <20171201012540.GA22663@jagdpanzerIV> (raw)
In-Reply-To: <CAOi56cVUBK-FhVxahmR_q1+466jr22wF3RbmcwpNTPayAB=xmw@mail.gmail.com>
Hello,
On (11/30/17 09:45), Kevin Hilman wrote:
[..]
> >> For kernelCI (part of how this thread got started):
> >>
> >> Acked-by: Kevin Hilman <khilman@baylibre.com>
> >> Reviewed-by: Kevin Hilman <khilman@baylibre.com>
> >>
> >> I also tested it on an arm64 platform with the new command-line arg:
> >>
> >> Tested-by: Kevin Hilman <khilman@baylibre.com>
> >
> > thanks.
>
> So do you plan to submit an official signed-off version of this?
> We're ready to use it ASAP in kernelCI.
yes, will do.
-ss
next prev parent reply other threads:[~2017-12-01 1:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOi56cVORdyjTXK4QGYRfyD1Q=QBgsU3B__gZT0xj6OBKaasLQ@mail.gmail.com>
[not found] ` <20171122015610.x3kgzqgtwywlurmz@wfg-t540p.sh.intel.com>
2017-11-22 3:27 ` kernel CI: printk loglevels in kernel boot logs? Fengguang Wu
2017-11-22 5:26 ` Sergey Senozhatsky
2017-11-22 10:42 ` Mark Brown
2017-11-22 11:34 ` Petr Mladek
2017-11-22 12:38 ` Sergey Senozhatsky
2017-11-22 12:52 ` Fengguang Wu
2017-11-23 2:59 ` Sergey Senozhatsky
2017-11-23 3:14 ` Fengguang Wu
2017-11-23 4:31 ` Sergey Senozhatsky
2017-11-29 0:13 ` Kevin Hilman
2017-11-29 7:25 ` Sergey Senozhatsky
2017-11-30 17:45 ` Kevin Hilman
2017-12-01 1:25 ` Sergey Senozhatsky [this message]
2017-11-23 10:04 ` Petr Mladek
2017-11-22 20:22 ` Kevin Hilman
2017-11-22 14:10 ` Fengguang Wu
2017-12-05 15:55 ` Petr Mladek
2017-12-05 16:13 ` Sergey Senozhatsky
2017-12-05 20:54 ` Steven Rostedt
2017-12-06 13:54 ` Petr Mladek
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=20171201012540.GA22663@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.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.