linux-kernel - Re: [PATCH v2] driver core: Fix device link device name collision

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <X/gNf4A6HwZTvNTU@kroah.com>
Date:   Fri, 8 Jan 2021 08:45:03 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Michael Walle <michael@...le.cc>
Cc:     Saravana Kannan <saravanak@...gle.com>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        stable <stable@...r.kernel.org>,
        Android Kernel Team <kernel-team@...roid.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] driver core: Fix device link device name collision

On Fri, Jan 08, 2021 at 02:10:51AM +0100, Michael Walle wrote:
> Am 8. Januar 2021 02:00:32 MEZ schrieb Saravana Kannan <saravanak@...gle.com>:
> >On Thu, Jan 7, 2021 at 4:43 PM Saravana Kannan <saravanak@...gle.com>
> >wrote:
> >Nevermind, I see it now. Also, in the future, if you can dump the logs
> >in some kind of pastebin site, that'd be nice. Avoid the emails
> >becoming unwieldy and also avoids the log lines from wrapping.
> 
> I thought about a pastebin. But then decided against it because they might be deleted in the future. So if anyone looking at the mail archives he might only get dead links. So.. 
> 
> dunno how this is handled on the LKML, tbh. 

Full logs are good, you did it right, Saravana can deal with long emails :)