Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20200521191800.136035-1-saravanak@google.com> <20200521191800.136035-2-saravanak@google.com>
 <20200715221356.GA219557@roeck-us.net>
In-Reply-To: <20200715221356.GA219557@roeck-us.net>
From:   Saravana Kannan <saravanak@google.com>
Date:   Wed, 15 Jul 2020 15:36:16 -0700
Message-ID: <CAGETcx_BTg5A7Cf8_Y61=_nUZJ4QVYXJwSOALvpZi8oDgm6Vng@mail.gmail.com>
Subject: Re: [PATCH v3 1/3] driver core: Expose device link details in sysfs
To:     Guenter Roeck <linux@roeck-us.net>
Cc:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "Rafael J. Wysocki" <rafael@kernel.org>,
        LKML <linux-kernel@vger.kernel.org>,
        John Stultz <john.stultz@linaro.org>,
        Android Kernel Team <kernel-team@android.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, Jul 15, 2020 at 3:14 PM Guenter Roeck <linux@roeck-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@google.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