All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Maxim Levitsky <mlevitsk@redhat.com>
Cc: linux-kernel@vger.kernel.org, rafael.j.wysocki@intel.com,
	sakari.ailus@linux.intel.com, heikki.krogerus@linux.intel.com,
	gregkh@linuxfoundation.org
Subject: Re: kernel oops in 'typec_ucsi' due to commit 'drivers property: When no children in primary, try secondary'
Date: Thu, 16 Jul 2020 21:33:06 +0300	[thread overview]
Message-ID: <20200716183306.GU3703480@smile.fi.intel.com> (raw)
In-Reply-To: <64a1ba836139b028936e24705eab06a032d598cf.camel@redhat.com>

On Thu, Jul 16, 2020 at 09:22:11PM +0300, Maxim Levitsky wrote:
> On Thu, 2020-07-16 at 21:21 +0300, Andy Shevchenko wrote:
> > On Thu, Jul 16, 2020 at 09:00:00PM +0300, Maxim Levitsky wrote:
> > > On Thu, 2020-07-16 at 18:47 +0300, Andy Shevchenko wrote:

...

> > > It works (no more oops)
> > 
> > Thanks for testing. I'm about to send formal patch, can you give your Tested-by tag there then?
> 
> Of course.
> 
> Tested-by: Maxim Levitsky <mlevitsk@redhat.com>

Thanks, I meant there [1] :-)

[1]: https://lore.kernel.org/lkml/20200716182747.54929-1-andriy.shevchenko@linux.intel.com/T/#u

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2020-07-16 18:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16  8:17 kernel oops in 'typec_ucsi' due to commit 'drivers property: When no children in primary, try secondary' Maxim Levitsky
2020-07-16  8:28 ` Greg KH
2020-07-16  8:47   ` Maxim Levitsky
2020-07-16 14:34 ` Andy Shevchenko
2020-07-16 17:59   ` Maxim Levitsky
2020-07-16 15:47 ` Andy Shevchenko
2020-07-16 18:00   ` Maxim Levitsky
2020-07-16 18:21     ` Andy Shevchenko
2020-07-16 18:22       ` Maxim Levitsky
2020-07-16 18:33         ` Andy Shevchenko [this message]

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=20200716183306.GU3703480@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=sakari.ailus@linux.intel.com \
    /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.