Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CA+3zgmsC2qKph_wDfknSa5eq6EnJqxzzj4K7G4_ZxGr5ZQTqbA@mail.gmail.com>
 <2023062256-walnut-pettiness-f4dc@gregkh>
In-Reply-To: <2023062256-walnut-pettiness-f4dc@gregkh>
From:   Tim Lewis <elatllat@gmail.com>
Date:   Fri, 23 Jun 2023 09:46:48 -0400
Message-ID: <CA+3zgmtGbwS+4VXhT4-G1sQyWFWKSPEu9hF3bkmaCNtagzXqig@mail.gmail.com>
Subject: Re: [PATCH 5.10 00/89] 5.10.185-rc1 review
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     osmtendev@gmail.com, open list <linux-kernel@vger.kernel.org>,
        stable@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Thu, Jun 22, 2023 at 3:36=E2=80=AFAM 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_cre=
ate_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