From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: kbuild-all@lists.01.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
kbuild test robot <lkp@intel.com>
Subject: Re: [PATCH v9] software node: add basic tests for property entries
Date: Thu, 12 Dec 2019 16:18:29 -0800 [thread overview]
Message-ID: <20191213001829.GG101194@dtor-ws> (raw)
In-Reply-To: <12135118.EjhP6glzqA@kreacher>
On Wed, Dec 11, 2019 at 11:53:05AM +0100, Rafael J. Wysocki wrote:
> On Monday, December 9, 2019 9:44:47 AM CET Rafael J. Wysocki wrote:
> > On Wed, Dec 4, 2019 at 7:53 PM Dmitry Torokhov
> > <dmitry.torokhov@gmail.com> wrote:
> > >
> > > This adds tests for creating software nodes with properties supplied by
> > > PROPERTY_ENTRY_XXX() macros and fetching and validating data from said
> > > nodes/properties.
> > >
> > > We are using KUnit framework for the tests.
> > >
> > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> >
> > Applied (as 5.5 material), thanks!
>
> And dropped again, because 0-day still complains.
>
> I'm going to push the rest of the series to Linus this week. The last patch
> can wait, even though it would be good to have it.
Could you point me to the 0-say compaint for the latest version as I did
not get it. I am still interested in sorting it all out.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-12-13 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 1:07 [pm:bleeding-edge 6/7] drivers/base/test/property-entry-test.c:454:1: warning: the frame size of 2960 bytes is larger than 2048 bytes kbuild test robot
2019-12-04 9:30 ` Rafael J. Wysocki
2019-12-04 18:53 ` [PATCH v9] software node: add basic tests for property entries Dmitry Torokhov
2019-12-09 8:44 ` Rafael J. Wysocki
2019-12-11 10:53 ` Rafael J. Wysocki
2019-12-13 0:18 ` Dmitry Torokhov [this message]
2019-12-13 10:15 ` Rafael J. Wysocki
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=20191213001829.GG101194@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rjw@rjwysocki.net \
/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).