[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAGETcx_BTg5A7Cf8_Y61=_nUZJ4QVYXJwSOALvpZi8oDgm6Vng@mail.gmail.com>
Date: Wed, 15 Jul 2020 15:36:16 -0700
From: Saravana Kannan <saravanak@...gle.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
John Stultz <john.stultz@...aro.org>,
Android Kernel Team <kernel-team@...roid.com>
Subject: Re: [PATCH v3 1/3] driver core: Expose device link details in sysfs
On Wed, Jul 15, 2020 at 3:14 PM Guenter Roeck <linux@...ck-us.net> wrote:
>
> Hi,
>
> On Thu, May 21, 2020 at 12:17:58PM -0700, Saravana Kannan wrote:
> > It's helpful to be able to look at device link details from sysfs. So,
> > expose it in sysfs.
> >
> > Say device-A is supplier of device-B. These are the additional files
> > this patch would create:
> >
> >
> > Signed-off-by: Saravana Kannan <saravanak@...gle.com>
>
> This patch creates a lot of noise in linux-next when booting various
> qemu images. Example log output as well as bisect results below.
> Reverting the patch fixes the problem.
Thanks for reporting it. Marek reported it last night too. I'll take a
look at this before the end of the week (probably tomorrow).
-Saravana
Powered by blists - more mailing lists