From: Tim Lewis <elatllat@gmail.com>
To: osmtendev@gmail.com, Greg KH <gregkh@linuxfoundation.org>
Cc: open list <linux-kernel@vger.kernel.org>, stable@vger.kernel.org
Subject: Re: [PATCH 5.10 00/89] 5.10.185-rc1 review
Date: Tue, 20 Jun 2023 09:25:52 -0400 [thread overview]
Message-ID: <CA+3zgmsC2qKph_wDfknSa5eq6EnJqxzzj4K7G4_ZxGr5ZQTqbA@mail.gmail.com> (raw)
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
20a22
> 5V: Failed to create debugfs directory
69a72
> FLASH_1V8: Failed to create debugfs directory
72a76
> HUB_5V: Failed to create debugfs directory
121a126,127
> TFLASH_VDD: Failed to create debugfs directory
> TF_IO: Failed to create debugfs directory
122a129
> USB_PWR_EN: Failed to create debugfs directory
123a131
> VCC_1V8: Failed to create debugfs directory
124a133
> VCC_3V3: Failed to create debugfs directory
125a135
> VDDAO_1V8: Failed to create debugfs directory
126a137
> VDDAO_3V3: Failed to create debugfs directory
127a139
> VDDCPU: Failed to create debugfs directory
278a291,292
> regulator-dummy: Failed to create debugfs directory
> regulator: Failed to create debugfs directory
kselftest 270 tests: diff ./out_5.10.184-rc1-dirty.txt
./out_5.10.185-rc1-dirty.txt
ltp 865 tests: diff ./out_5.10.184-rc1-dirty.txt ./out_5.10.185-rc1-dirty.txt
next reply other threads:[~2023-06-20 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 13:25 Tim Lewis [this message]
2023-06-22 7:36 ` [PATCH 5.10 00/89] 5.10.185-rc1 review Greg KH
2023-06-23 13:46 ` Tim Lewis
-- 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+3zgmsC2qKph_wDfknSa5eq6EnJqxzzj4K7G4_ZxGr5ZQTqbA@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).