From: Tim Lewis <elatllat@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: osmtendev@gmail.com, open list <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 5.10 00/89] 5.10.185-rc1 review
Date: Fri, 23 Jun 2023 09:46:48 -0400 [thread overview]
Message-ID: <CA+3zgmtGbwS+4VXhT4-G1sQyWFWKSPEu9hF3bkmaCNtagzXqig@mail.gmail.com> (raw)
In-Reply-To: <2023062256-walnut-pettiness-f4dc@gregkh>
On Thu, Jun 22, 2023 at 3:36 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Tue, Jun 20, 2023 at 09:25:52AM -0400, Tim Lewis wrote:
> > Is it intentional and acceptable for dmesg to now log 14 "Failed to
> > create debugfs directory" messages?
> >
> > I assume it's related to "regulator: Fix error checking for debugfs_create_dir".
> >
> > dmesg 398 lines: diff ./5.10.184-rc1-dirty.txt ./5.10.185-rc1-dirty.txt
> > 19a20
> > > 12V: Failed to create debugfs directory
>
> Do you also see this issue in newer kernel releases?
>
> thanks,
>
> greg k-h
Yes;
# uname -r
6.3.9-dirty
# dmesg | grep -c "Failed to create debugfs directory"
13
next prev parent reply other threads:[~2023-06-23 13:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 13:25 [PATCH 5.10 00/89] 5.10.185-rc1 review Tim Lewis
2023-06-22 7:36 ` Greg KH
2023-06-23 13:46 ` Tim Lewis [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-19 10:29 Greg Kroah-Hartman
2023-06-19 13:20 ` Florian Fainelli
2023-06-20 9:18 ` Chris Paterson
2023-06-20 10:21 ` Jon Hunter
2023-06-20 11:04 ` Sudip Mukherjee (Codethink)
2023-06-20 14:37 ` Naresh Kamboju
2023-06-20 17:08 ` Allen Pais
2023-06-20 21:04 ` Shuah Khan
2023-06-21 0:38 ` Guenter Roeck
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=CA+3zgmtGbwS+4VXhT4-G1sQyWFWKSPEu9hF3bkmaCNtagzXqig@mail.gmail.com \
--to=elatllat@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osmtendev@gmail.com \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).