From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Shuah Khan <skhan@linuxfoundation.org>, Petr Mladek <pmladek@suse.com>
Cc: brendanhiggins@google.com, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: kunit stopped working
Date: Mon, 21 Dec 2020 22:03:32 +0200 [thread overview]
Message-ID: <20201221200332.GB4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201221194008.GA4077@smile.fi.intel.com>
On Mon, Dec 21, 2020 at 09:40:08PM +0200, Andy Shevchenko wrote:
> +Cc people from culprit commit
Guys, revert helps. I am open to test any solution you may propose, thanks!
...
> # first bad commit: [757055ae8dedf5333af17b3b5b4b70ba9bc9da4e] init/console: Use ttynull as a fallback when there is no console
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-12-21 20:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 14:43 kunit stopped working Andy Shevchenko
2020-12-21 14:45 ` Andy Shevchenko
2020-12-21 18:37 ` Shuah Khan
2020-12-21 19:27 ` Andy Shevchenko
2020-12-21 19:40 ` Andy Shevchenko
2020-12-21 20:03 ` Andy Shevchenko [this message]
2020-12-22 1:43 ` David Gow
2020-12-22 1:43 ` David Gow
2020-12-22 7:26 ` David Gow
2020-12-22 7:26 ` David Gow
2020-12-22 13:34 ` Andy Shevchenko
2020-12-22 13:34 ` Andy Shevchenko
2020-12-27 19:58 ` Brendan Higgins
2020-12-27 19:58 ` Brendan Higgins
2021-01-05 16:17 ` Petr Mladek
2021-01-05 16:17 ` Petr Mladek
2021-01-05 16:49 ` Petr Mladek
2021-01-05 16:49 ` Petr Mladek
2021-01-06 4:04 ` Sergey Senozhatsky
2021-01-06 4:04 ` Sergey Senozhatsky
2021-01-06 13:10 ` Petr Mladek
2021-01-06 13:10 ` Petr Mladek
2021-01-07 7:15 ` Sergey Senozhatsky
2021-01-07 7:15 ` Sergey Senozhatsky
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=20201221200332.GB4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brendanhiggins@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pmladek@suse.com \
--cc=skhan@linuxfoundation.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.