From: Shuah Khan <skhan@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Brendan Higgins <brendanhiggins@google.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] KUnit fixes update for Linux 5.17-rc4
Date: Thu, 10 Feb 2022 13:02:20 -0700 [thread overview]
Message-ID: <3a0311b2-33af-d13e-e92b-111bfb357a19@linuxfoundation.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
Hi Linus,
Please pull the following KUnit fixes update for Linux 5.17-rc4.
This KUnit fixes update for Linux 5.17-rc4 consists of bug fixes
to the test and usage documentation.
Note: The doc fix patch resolves a bugzilla issue.
diff is attached.
thanks,
-- Shuah
----------------------------------------------------------------
The following changes since commit 235528072f28b3b0a1446279b7eaddda36dbf743:
kunit: tool: Import missing importlib.abc (2022-01-25 12:59:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest tags/linux-kselftest-kunit-fixes-5.17-rc4
for you to fetch changes up to 92a68053c3468705e2c7c752c9a3f256304a35a6:
Documentation: KUnit: Fix usage bug (2022-02-08 13:16:20 -0700)
----------------------------------------------------------------
linux-kselftest-kunit-fixes-5.17-rc4
This KUnit fixes update for Linux 5.17-rc4 consists of bug fixes
to the test and usage documentation.
----------------------------------------------------------------
Akira Kawata (1):
Documentation: KUnit: Fix usage bug
Daniel Latypov (1):
kunit: fix missing f in f-string in run_checks.py
Documentation/dev-tools/kunit/usage.rst | 2 +-
tools/testing/kunit/run_checks.py | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------
[-- Attachment #2: linux-kselftest-kunit-fixes-5.17-rc4.diff --]
[-- Type: text/x-patch, Size: 979 bytes --]
diff --git a/Documentation/dev-tools/kunit/usage.rst b/Documentation/dev-tools/kunit/usage.rst
index 76af931a332c..1c83e7d60a8a 100644
--- a/Documentation/dev-tools/kunit/usage.rst
+++ b/Documentation/dev-tools/kunit/usage.rst
@@ -242,7 +242,7 @@ example:
int rectangle_area(struct shape *this)
{
- struct rectangle *self = container_of(this, struct shape, parent);
+ struct rectangle *self = container_of(this, struct rectangle, parent);
return self->length * self->width;
};
diff --git a/tools/testing/kunit/run_checks.py b/tools/testing/kunit/run_checks.py
index 4f32133ed77c..13d854afca9d 100755
--- a/tools/testing/kunit/run_checks.py
+++ b/tools/testing/kunit/run_checks.py
@@ -61,7 +61,7 @@ def main(argv: Sequence[str]) -> None:
elif isinstance(ex, subprocess.CalledProcessError):
print(f'{name}: FAILED')
else:
- print('{name}: unexpected exception: {ex}')
+ print(f'{name}: unexpected exception: {ex}')
continue
output = ex.output
next reply other threads:[~2022-02-10 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 20:02 Shuah Khan [this message]
2022-02-11 0:07 ` pr-tracker-bot
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=3a0311b2-33af-d13e-e92b-111bfb357a19@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=brendanhiggins@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®