From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Maxime Ripard <mripard@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org, Maxime Ripard <maxime@cerno.tech>
Subject: Re: [PATCH RESEND 2/2] drivers: base: Add basic devm tests for platform devices
Date: Sat, 3 Jun 2023 16:38:55 +0200 [thread overview]
Message-ID: <2023060332-devoutly-elusive-6cd7@gregkh> (raw)
In-Reply-To: <20230329-kunit-devm-inconsistencies-test-v1-2-015b1574d673@kernel.org>
On Fri, Jun 02, 2023 at 05:20:44PM +0200, Maxime Ripard wrote:
> From: Maxime Ripard <maxime@cerno.tech>
>
> Platform devices show some inconsistencies with how devm resources are
> released when the device has been probed and when it hasn't. Let's add a
> few tests to exercise thos paths and odd cases.
"those" :)
And what are those inconsistencies? Where are they documented? Here or
somewhere else?
thanks,
greg k-h
prev parent reply other threads:[~2023-06-03 14:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 15:20 [PATCH RESEND 0/2] drivers: base: Add tests showing devm handling inconsistencies Maxime Ripard
2023-06-02 15:20 ` [PATCH RESEND 1/2] drivers: base: Add basic devm tests for root devices Maxime Ripard
2023-06-02 18:02 ` kernel test robot
2023-06-02 21:09 ` Daniel Latypov
2023-06-03 14:43 ` Greg Kroah-Hartman
2023-06-04 8:31 ` Maxime Ripard
2023-06-07 19:14 ` Greg Kroah-Hartman
2023-06-08 7:59 ` Maxime Ripard
2023-06-02 15:20 ` [PATCH RESEND 2/2] drivers: base: Add basic devm tests for platform devices Maxime Ripard
2023-06-03 14:38 ` Greg Kroah-Hartman [this message]
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=2023060332-devoutly-elusive-6cd7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mripard@kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.