From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: Tree for Jul 4
Date: Thu, 4 Jul 2019 22:24:50 +1000 [thread overview]
Message-ID: <20190704222450.021c9d71@canb.auug.org.au> (raw)
In-Reply-To: <20190704220945.27728dd9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
Hi all,
This release produces a whole lot (over 200) of this message in my qemu
boot tests:
[ 1.698497] debugfs: File 'sched' already present!
Introduced by commit
43e23b6c0b01 ("debugfs: log errors when something goes wrong")
from the driver-core tree. I assume that the error(?) was already
happening, but it is now being reported.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-07-04 12:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 12:09 linux-next: Tree for Jul 4 Stephen Rothwell
2019-07-04 12:24 ` Stephen Rothwell [this message]
2019-07-04 12:40 ` Greg Kroah-Hartman
2019-07-06 8:34 ` Greg Kroah-Hartman
2019-07-06 9:44 ` Stephen Rothwell
2019-07-06 9:46 ` Greg Kroah-Hartman
2019-07-06 10:17 ` Stephen Rothwell
2019-07-06 14:33 ` Greg Kroah-Hartman
2019-07-06 15:42 ` Greg Kroah-Hartman
2019-07-05 8:59 ` linux-next: Tree for Jul 4 -> conflict between s390 and driver-core tree Christian Borntraeger
2019-07-08 11:20 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-07-04 10:51 linux-next: Tree for Jul 4 Stephen Rothwell
2023-07-04 3:43 Stephen Rothwell
2022-07-04 8:21 Stephen Rothwell
2018-07-04 5:57 Stephen Rothwell
2017-07-04 5:44 Stephen Rothwell
2016-07-04 8:43 Stephen Rothwell
2014-07-04 6:42 Stephen Rothwell
2014-07-04 8:42 ` Sachin Kamat
2014-07-04 15:10 ` Stephen Rothwell
2014-07-05 0:48 ` J. Bruce Fields
2014-07-05 14:57 ` Sachin Kamat
2014-07-06 4:54 ` Nick Krause
2014-07-06 5:17 ` Nick Krause
2014-07-06 5:21 ` Nick Krause
2014-07-06 5:34 ` Nick Krause
2014-07-06 5:42 ` Nick Krause
2014-07-05 14:56 ` Sachin Kamat
2013-07-04 6:06 Stephen Rothwell
2013-07-04 7:41 ` Sedat Dilek
2013-07-04 8:21 ` Sedat Dilek
2013-07-04 8:40 ` Sedat Dilek
2013-07-04 8:45 ` Andrew Morton
2013-07-04 9:12 ` Sedat Dilek
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=20190704222450.021c9d71@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox